Ban "plain" Guice; downgrade it to 5.1.0

[cstamas]

Current master uses Guice 6 and this has following consequences:

• jakarta.inject ends up in /lib of Maven distro: it is a transitive dep of Guice 6
• excluding it is not possible, as it is needed at compile and runtime (com.inject.guice.Provider extends both Providers from javax and jakarta).
• we do not require any feature of Guice 6: while Eclipse Sisu may "open" toward javax.inject, Maven JSR330 is here only for Maven 3 backward compatibility, while "native" Maven 4 stuff has Maven DI in place. Best to keep it aligned with Maven 3.9.x line.

---

Changes:

• downgrade Guice to 5.1.0 (same as in latest Maven 3.9.x)
• remove depMgt for "main" Guice JAR, offer only the one with "classess" classifier (ASM-less one)
• ban main Guice JAR to make sure does not enter the game by mistake

[slachiewicz]

In general ok, but what to do with external components that may be injected? Keep it in javax.inject?

[cstamas]

jakarta package name was never exported from maven core, but it was present in core. so nothing was able to use it anyway.