Enforce minor version changes and eLab 5.5 support

[mhxion]

Better Version Enforcing

Given @NicolasCARPi's word elabftw/elabftw#6581 (comment) that minor version updates wouldn't break APIs ;) we can now confidently enforce the minor versions. This PR adds support for abort_minor_only and warn_minor_only for the elab_strict_version_match configuration field.

# elapi.yml
elab_strict_version_match: warn_minor_only

warn_minor_only is also now the default value for when elab_strict_version_match doesn't exist. The *_minor_only value is triggered when the installed minor version X.Y.Z -> X.Y doesn't match elAPI's most supported version A.B. With abort_minor_only elAPI will show an error and quit, with warn_minor_only elAPI will show a warning and let the API request go through anyway. elab_strict_version_match: abort now can be seen as the more aggressive counterpart where the whole version string X.Y.Z must match.

This also means we need not to worry about falling behind adding version strings to elAPI as soon as eLabFTW updates.

Recent Versions Support

This PR adds support for eLabFTW 5.4 - 5.5.5. So far no breaking changes. All plugins and examples are working without changes.

[alexander-haller]

warn_minor_only as the new default 👍
TY!

[mhxion]

I updated the description to add elab_strict_version_match: warn_minor_only.