add properties for graalvm

[XenoAmess]

as title.
at least usable in my repo.

[bdemers]

I'm a native-image fan, but this type of thing has always been the hard part.

My main concern is we want to make sure it's easy to maintain as the codebase evolves

[bdemers]

There are a handful of services, though these should possibly live in their corresponding module, and not in jjwt-api, thoughts?

./impl/src/main/resources/META-INF/services/io.jsonwebtoken.CompressionCodec
./extensions/gson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Serializer
./extensions/gson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Deserializer
./extensions/orgjson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Serializer
./extensions/orgjson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Deserializer
./extensions/jackson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Serializer
./extensions/jackson/src/main/resources/META-INF/services/io.jsonwebtoken.io.Deserializer

[XenoAmess]

I put it all in -api for maintaner to maintain them easier, no need to worry about what modification shall look for which json
but yes, logically it should be split into each module

[XenoAmess]

I would like to try to write a maven-plugin to auto-generate it, so the two problems shall both be solved.

[bdemers]

Any thoughts on generating this list at build time?
This is going to be difficult to maintain and track if/when these method signatures change.

Any ideas on creating a test harness? (Extra points if it doesn't require slowly creating a native image in order to test it).

[XenoAmess]

as for generating I have no idea either, maybe I have to make another maven-plugin for it.
for test, unfortunatly I have no idea how to make it test native fastly.
the native image building is...well, slow.