Adding support for SequencedCollection, SequencedSet and SequencedMap from JDK 21

[msamoylych]

Adding support for java.util.SequencedCollection, java.util.SequencedSet and java.util.SequencedMap from JDK 21 for @Singular annotation (@Builder)

[rspilker]

Thanks for the contribution! I haven't reviewed the whole code yet.

I did copy the java 22 gradle fix directly to master, thanks for that solution, because it's not part of this fix. Please remove it from this pull request.

[Rawi01]

• Please add yourself to the AUTHORS file
• You have disabled the Eclipse test. My guess is that you did this to avoid the error messages about missing classes. There are two ways to handle this:
  • Add the test, mark the errors as expected and call it a day
  • Add the current runtime to the eclipse compiler classpath. IIRC this will cause some split module errors. The last time I managed to workaround it but I think in this case we can no longer do so and have to change something somewhere
• I think the mapping between the sorted guava type and the sequenced collections is incorrect. There also is no test for this, do we ever call this?
• +1 for updating the website

[msamoylych]

You have disabled the Eclipse test. My guess is that you did this to avoid the error messages about missing classes. There are two ways to handle this:
Add the test, mark the errors as expected and call it a day
Add the current runtime to the eclipse compiler classpath. IIRC this will cause some split module errors. The last time I managed to workaround it but I think in this case we can no longer do so and have to change something somewhere

Eclipse IDE 2023-12 test uses JDK 21 unless specified compiler.compliance.level but in ant.yml is specified JDK 17 to run this test. Therefore BuilderSingularSequencedCollections test performs (// version 21:) and fails due to error messages about missing classes in JDK 17.
I added the test with expected errors

I think the mapping between the sorted guava type and the sequenced collections is incorrect. There also is no test for this, do we ever call this?

There are no other suitable classes in Guava now. I think BuilderSingularRedirectToGuava test is sufficient