Specifying maximum version of plugin to prevent installation on versions of BTCPay they would break on

[rockstardev]

A useful additional feature would be the ability to set a maximum version for a plugin when a new version is released. This way, if a plugin becomes incompatible or breaks with newer versions, it would stop appearing in the list for users running a version above the set limit. This could be managed through the UI of the plugin builder, ensuring users only see compatible plugins.

[pavlenex]

cc @NicolasDorier

[NicolasDorier]

Additional use of the max version: A BTCPay Server restarting after a version up could query the plugin-builder and preemptively disable plugins rather than waiting for them to crash.