Fixing MP 6.0 Issues

[JanWesterkamp-iJUG]

To create a new release that can pass the 2nd ballot of MP 6.0 hopefully, I created this issue.
We have the following options:

• Regarding the email from Wayne today, we can just restart the ballot with all current members eligible to vote
• We can create a new MP 6.0 version with fixes for my findings on the review (I created a PR for it: MP 6 Issues PR #298)
• We can add an updated version of MP Metrics 5.0 with having dependencies to Jakarta EE 10 component specs (Jakarta REST and CDI especially) again instead of the whole Jakarta EE 10 Core Profile - which would make it easier for vendors to fulfil the requirements to be compatible
• We can restart the Plan Review with an updated plan, especially regarding MP Metrics and it's dependencies from other MP component specs

The first option is the simplest one, but with potentially a "even good enough" result.
The second one could fix my concerns, at least the ones I can see as a quick fix. Both two options would make it possible to get a MP 6.0 release this year as Xmas present potentially.
To make it simpler to be compatible with MP Metrics 5.0 and if included in MP 6.0 (as Service Release) that could help implementations, that are now not compatible to Jakarta EE 10 Core Profile. This will take us to somewhere in Q1 2023.
When we want to make everybody happy - we need to plan a complete new release with major changes regarding MP Metrics (i.e. make it optional, remove it from the MP Platform, replace it by OpenTelemetry Metrics in a new MP Telemetry release, update all dependent specs and TCKs etc.). This can take a while (i.e. OpenTelemetry is not stable regarding telemetry data yet) and would prevent us and the users to have a MP Platform release available that alignes with Jakarta EE 10 - the worst outcome from my perspective, especially with respect to the current discussion about MP JWT and Jakarta Security!
We better do plan a new, additional release later to go into this direction, when there is a replacement available - like we did with MP OpenTracing and MP Telemetry (Tracing).

So @Emily-Jiang and me prefer heading towards option two soon and work on three and four then.
What do you think about it?