classfile reader: handle JDK 9+ constant types in constant pool

[SethTisue]

forward-port of scala/scala#10675 and scala/scala#8595
references scala/bug#12396 and scala/bug#11635
fixes #19527 ("bad constant pool tag 17")
also fixes unreported potential "bad constant pool tag 19" and "bad constant pool tag 20" errors

should be backported to 3.3.x, IMO

[SethTisue]

as far as I know, this repo doesn't have a mechanism for restricting a test to run only on JDK 21+, so I put it in tests/disabled

I did verify locally, on JDK 21, that the test failed before the change and succeeded afterwards

marking as draft for now, pending review of the Scala 2 PR

[som-snytt]

@SethTisue there is // test: -jvm 11+

[SethTisue]

thx @som-snytt — I've updated the PR to use that.

[SethTisue]

I've added a commit forward-porting @lrytz's ClassfileParserTest, which will let us know if ASM adds any further such constants

[SethTisue]

I've converted this back to a draft, because in porting Lukas's test, I noticed that Dotty's ClassfileConstants is lacking CONSTANT_MODULE and CONSTANT_PACKAGE. Need to look into why that is and whether it matters....

[SethTisue]

Okay, I went back and added the additional constants from scala/bug#11635 . I did not forward-port the additional test from scala/scala#8595 . It is Scaladoc-based and did not trigger the bug on Scala 3, and I don't know how else to trigger it.

[SethTisue]

@Kordyjan should I backport it myself, or just figure it will happen...?

[Kordyjan]

I will handle that before 3.3.3.