This PR introduces changes to better support Key Rotation.

Super classes

JWT no longer implements DecodedJWT. Users who find this breaking need to update the return type of JWT.decode() and JWT.require() ... verify() to DecodedJWT instead of JWT.

JWT parts

Before this PR the DecodedJWT instance just allowed to obtain the original version of the token and the signature (third part). Now 2 more methods were added: getHeader() and getPayload() which return the first and second part of the header as it is, with a Base64 encoding.

KeyProvider refactor

Now receives a "Key Id" when asked for the PublicKey, and also asks for a "Signing Key Id" that will be set in the header of the token in the signing process. If the "Key Id" is being set by the user using the withKeyId() in the JWTCreator class, the library won't overwrite it with the one defined in the KeyProvider implementation.
Users who doesn't use KeyProvider (i.e. instantiate the algorithm by passing just the keys) or return null in the getSigningKeyId() call will not be affected by this and the kid claim won't be automatically set.

Example usage:

final MyOwnJwkProvider jwkProvider = new MyOwnJwkProvider("{JWKS_FILE_HOST}");
final RSAPrivateKey privateKey = //Get the key instance
final String privateKeyId = //Create an Id for the above key

RSAKeyProvider keyProvider = new RSAKeyProvider() {
    @Override
    public RSAPublicKey getPublicKeyById(String kid) {
        //Value might be null if it wasn't defined in the Token's header
        Jwk jwk = jwkProvider.get(keyId);
        return (RSAPublicKey) jwk.getPublicKey();
    }

    @Override
    public RSAPrivateKey getPrivateKey() {
        return privateKey;
    }
    
    @Override
    public String getPrivateKeyId() {
        return privateKeyId;
    }
};
Algorithm algorithm = Algorithm.RSA256(keyProvider);
//Use the Algorithm to create and verify JWTs.

Algorithms

The Algorithm#verify method changed it's signature: Now it will verify a given DecodedJWT instance instead of the byte[] of signature and contents. This was needed to get the "Key Id" claim and request it's associated PublicKey to the KeyProvider. Although this is a breaking change, users shouldn't be using the Algorithm class directly as it's purpose is to be called internally by the library.