Clarify JPMS requirements on platform Wiki across all runtimes, EE, SE, ...

[starksm64]

Is your feature request related to a problem? Please describe.
The Modularized Jars page on the wiki only talks about "Jakarta EE run-times" support of JPMS. The question was raised about Java SE based run modes as well since there are several specs that support usage in such environments.

Describe the solution you'd like
The wiki page should be updated for the common platform expectations across all runtime modes.

Additional context
There is a Jakarta Activation challenge regarding assumptions about the TCK being able to use JPMS and further questions on whether there should be different behaviors when running under a EE container runtime vs a Java SE environment.

AB#67

[starksm64]

Based on the discussions around the requirements for JPMS in EE10, the main critique to requirements regarding JMPS was that runtimes and alternative sources of API jars wanted the ability to use JPMS. The equates to extending the wiki statement to include all environments a given specification can be tested under. An initial proposed change would simply to be:

Change: no requirement for Jakarta EE run-times to support JPMS
to: "no requirement for Jakarta EE or Java SE run-times to support JPMS"

[dblevins]

Agree with this proposed change. We do have an activation jar and it does not support JPMS. We also frequently ship it in an uber jar.