Jakarta specs management issues

1. There are some specs, like activation and resources, iirc, for which strange "implementation" artifacts exist (having glassfish or com.sun groupids ) which include both impl and api classes. In such case we should probably also ban/exclude the corresponding jakarta spec artifact, which we do not do yet, and Quarkus doesn't either.

2. We should go through the whole list of specs and decide for each one which we prefer and make sure that we ban all others. We'd typically prefer the jakarta one and ban all from javax, jboss, geronimo and glassfish. Although sometimes we prefer jboss or glassfish following the preference of Quarkus. Perhaps checking jars for overlapping packages/classes would help.

Start by reviewing the project's complete Jakarta specification dependency list and compare it with Quarkus's preferences. Inspect the relevant jars for overlapping packages and classes, then define and apply a preferred artifact for each specification while excluding the unwanted javax, jboss, geronimo, glassfish, or implementation artifacts.

Written by the indexing model from the issue text.