chore: plugin compatibility infos

[alfredotoselli]

Description

Added min and max version on plugin manifest.
If we agree on the structure I'll update admin-vue and ts-client (Plugin.ts type)

We want to enforce it? e.g. on plugin installation or activation (Not necessary for me)

Related to issue #960

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas

[lucagobbi]

I wouldnt enforce it for the moment, maybe a warning in the admin or in the logs?

[pieroit]

No enforcing, will make things way more complicated

[pieroit]

Thanks @alfredotoselli left some change request

[pieroit]

Please keep the structure flat for the moment, maybe with a more explicit naming, i.e.
version, ..., min_cat_version, max_cat_version

[pieroit]

maybe empty string as default value, we made a mess in the past with a different default for every key XD

[alfredotoselli]

agree, also easier to handle in admin-vue

[alfredotoselli]

Here is admin-vue PR

About an eventual warning we could:

• check the versions on get_available_plugins API, log a warning and return the info to be used by admin-vue
• check the version somewhere else in BE, just log a warning
• check the version at FE, showing a warning only in admin vue
• not doing it at all

[pieroit]

Here is admin-vue PR

About an eventual warning we could:

• check the versions on get_available_plugins API, log a warning and return the info to be used by admin-vue
• check the version somewhere else in BE, just log a warning
• check the version at FE, showing a warning only in admin vue
• not doing it at all

Thanks @alfredotoselli, just merged.

Let's see what the contribs think about the strategy here.
Any take of responsibility on plugin compatibility is going to cost maintaining, so my preference is on waiting to better focus and with some feedback at hand