Fix IllegalArgumentException when using EdDSA signature algorithm

[0rzech]

This fixes java.lang.IllegalArgumentException: No enum constant io.smallrye.jwt.algorithm.SignatureAlgorithm.EdDSA when EDDSA is set through
smallrye.jwt.new-token.signature-algorithm property, or when it is set with
JwtClaimsBuilderImpl.

Currently, JwtSignatureImpl.getConfiguredSignatureAlgorithm() returns
algorithm name as a String from SignatureAlgorithm.algorithmName field,
in case of it being loaded from a configuration file.

If the algorithm was set through JwtClaimsBuilderImpl, the value is returned
as-is from the header, which means EdDSA, because this is how
JwtClaimsBuilderImpl puts the value there.

This name is then used to get appropriate SignatureAlgorithm enum variant
in JwtSignatureImpl.getSigningKeyFromKeyContent(String), but without
using toUpperCase() on the name, causing exception when EdDSA is used.

The fix adds toUpperCase() call on algorithm name before passing it
to SignatureAlgorithm.valueOf(String).

[sberyozkin]

@0rzech Thanks for your help and patience with fixing this issue.

Before I merge, can you give me a favor and squash commits, and have IllegalStateException thrown indirectly by adding it to https://github.com/smallrye/smallrye-jwt/blob/main/implementation/jwt-build/src/main/java/io/smallrye/jwt/build/impl/ImplMessages.java instead

Thanks

[sberyozkin]

@0rzech You may still have to make these two latest tests conditional as Java 11 is still required, let me run the build

[sberyozkin]

Looks like so

[0rzech]

@0rzech Thanks for your help and patience with fixing this issue.

Before I merge, can you give me a favor and squash commits, and have IllegalStateException thrown indirectly by adding it to https://github.com/smallrye/smallrye-jwt/blob/main/implementation/jwt-build/src/main/java/io/smallrye/jwt/build/impl/ImplMessages.java instead

Thanks

I can't put it there, because it would create circular library dependency. I have wrapped all calls to fromAlgorithm(String algorithmName) in appropriate try/catch clauses instead.

@0rzech You may still have to make these two latest tests conditional as Java 11 is still required, let me run the build

Looks like so

Whoops, sorry for that. I tried to avoid post-Java-11 features. Which part have I overlooked? Do you mean running tests conditional on JRE version? If yes, then I've added min 17 condition to new tests.