Allow easy development of plugins locally

[jgbernalp]

Currently Perses plugins use module federation to share dependencies and allow them to be injected into Perses UI (or other clients). In order to make development simple we can use the development server from the plugin side and adjust Perses Backend to run in a "plugin development mode" that will proxy requests of the /plugin endpoint to the plugin development server. As follows:

Remaining work:

• Create a single server to be able to host several plugins at once: currently the dev server runs per plugin: Add a single dev server for all plugins #58
• Adjust Perses backend to include development plugins when listing: /api/plugins: [ENHANCEMENT] Improve the way the plugins are loaded by considering the local path where they are stored perses#2626
• Adjust Perses backend to proxy plugin files request to the plugin dev server: [ENHANCEMENT] Improve the way the plugins are loaded by considering the local path where they are stored perses#2626

Open questions:

• Can we load dynamically cue files on the backend while developing plugins?

[Nexucis]

when you are referring to a dev server are you talking about the one created when running npm run dev ?

Can we load dynamically cue files on the backend while developing plugins?

Not yet but yeah that will be the plan

[jgbernalp]

when you are referring to a dev server are you talking about the one created when running npm run dev ?

Yes from the plugin side