JRuby bump causes CI failures

[Earlopain]

Upgrading from 10.0.5.0 to 10.1.0.0 causes the following error in the wasm bindings:
(https://github.com/ruby/prism/actions/runs/26855989543/job/79198822453?pr=4121)

java.lang.NoSuchMethodError: 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
	at org.ruby_lang.prism.wasm.PrismParser.builder(PrismParser.java:92)
	at org.ruby_lang.prism.wasm.Prism.<init>(Prism.java:24)
	at org.ruby_lang.prism.wasm.Prism.<init>(Prism.java:19)
	at org.jruby.parser.prism.JRubyTest$TestingPrism.<init>(JRubyTest.java:89)
	at org.jruby.parser.prism.JRubyTest.jrubyReproducer(JRubyTest.java:99)

Error:  Errors: 
Error:    JRubyTest.jrubyReproducer:99 » NoSuchMethod 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
Error:    WASMTest.test1:35 » NoSuchMethod 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
Error:    WASMTest.test2:51 » NoSuchMethod 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
Error:    WASMTest.testMBCIdentifier:67 » NoSuchMethod 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
Error:    WASMTest.testVersion:79 » NoSuchMethod 'io.roastedroot.redline.UniversalInstance$Builder io.roastedroot.redline.UniversalInstance.builder(com.dylibso.chicory.wasm.WasmModule)'
[INFO] 
Error:  Tests run: 5, Failures: 0, Errors: 5, Skipped: 0

I have ignored dependabot jruby updates. Once jruby is bumped manually, dependabot should start up again by itself but better be sure by pinging it with @dependabot unignore org.jruby:jruby-complete

cc @headius

[headius]

Thanks for the ping, I'll look into it.

[headius]

The issue appears to be a conflict between the redline shipped in JRuby and the redline shipped with Prism when verifying this logic. They are probably loading pieces of the library from different classloaders and then it is unable to find a matching method from one classloader for arguments from a different classloader.

Modifying JRuby to relocate the built-in redline to a different, internal package appears to fix it. This will be applied for JRuby 10.1.1.0 and available when that is released (probably in the next week).