Adding support for multiple keys during parsing

[faogustavo]

• Created SigningKey and EncryptionKey
• Those new types will be the default values used to sign and verify the keys
• They already include the algorithm used, and have subtypes to handle signing/encrypt/verify/decrypt
• Created JwtKeyRegistry to store multiple keys
• The registry can be used both during creation and validation of JWTs
• Users can create and maintain these registries on their own and provide us an instance to sign/verify
• Added KeyID support
• Now, if the JWT has the kid header, the key with that id in the registry will take precedence to be used
• If there is no key with same id, it will fallback to the default key for the defined algorithm
• Created new helper functions on top of the Signing and Encryption algorithms.
• You can use the algorithm to generate or parse a key
• Added tests to all new features and improved old tests by using the new keys helpers

[github-actions]

	Tests	Passed ✅	Skipped	Failed
JUnit Test Report	1040 ran	1040 passed	0 skipped	0 failed

• View JUnit Test Report