Add capability of specifying JWT decode algorithm

[santiagorodriguez96]

Summary

This PR allow users of the gem to be able to specify the JWT decode algorithm when downloading a TOC. I let the default be RS256 which is the one that the MSD3 BLOB uses but I'm open to change it.

The reason behind this change is that users might have to download TOC from other endpoints different than the MSD3 BLOB which neeed to be decoded with a different algorithm:

~/.gem/ruby/3.2.2/gems/jwt-2.2.1/lib/jwt/decode.rb:40:in `verify_signature': Expected a different algorithm (JWT::IncorrectAlgorithm)
	from ~/.gem/ruby/3.2.2/gems/jwt-2.2.1/lib/jwt/decode.rb:26:in `decode_segments'
	from ~/.gem/ruby/3.2.2/gems/jwt-2.2.1/lib/jwt.rb:28:in `decode'
	from ~/.gem/ruby/3.2.2/fido_metadata/lib/fido_metadata/client.rb:28:in `download_toc'