Looks like:
- Module system and shading do not mix well, and
- Current setup in 3.0 for Afterburner produces badly broken jar
To solve (2), I think we might as well remove shading of ByteBuddy.
Also worth considering that Afterburner may not really work that well on JDKs 17 and beyond so optimizing Afterburner packaging may not be worth much effort.