Minimum Java version support for home modules

[jmcc0nn3ll]

Jetty version
Jetty 10 - Jetty 11

Java version
Java 16+

OS type/version
N/A

Description
Now that additional features are really starting to show up in incremental releases of Java releases, we should have a mechanism in our module system that allows for a minimum java version for the enabling and execution of a module. On the enabling side we should test the java version and fail if it isn't sufficient to enable. On the execution side we should fail the start up if the module is enabled but the executing java version is not sufficient indicating the user setup the base with one java version and tried to start it with another one that doesn't carry the feature.

This would require updates to the documentation as well.

[sbordet]

Rather than a new section in *.mod files, we can use the "runtime feature" introduced in #5492 that we currently use in Jetty 9.4.x for ALPN, where we have alpn-available-[true|false].mod files.

[github-actions]

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been closed due to it having no activity.