Add a plugin architecture for future extensions #54
Description
There are many possible future extensions which are possible for the krillnotes application. However some of them may have commercial applications and therefore shouldn't be integrated into the open source core of krillnotes.
Therefore it is important to think about a possible plugin structure which caters for plugins which extend:
- the krillnotes-core written in Rust
- the krillnotes-desktop layer based on Tauri v2 and written in Rust and Typescript
A plugin architecture would be able to apply functionality to both layers by using clearly documented communication protocols and API interfaces.
Possible plugins:
- swarm-sync p2p sharing of workspaces
- integration of geospatial information on notes (lat/long) with offline/online map services, eg. Leaflet
- integration of online sources into the app
- Bespoke import/export functionality, eg. export or sync workspace with PgSQL, export all notes to DOCX