fix(storage): parse enums properly

[Caceresenzo]

Fix incorrect parsing of the OTP algorithm introduced in version 8.0.0 to enable this feature.

The code before (in v7.0.0):

Authenticator/src/models/storage.ts

Lines 383 to 384 in bf630cc

	data[hash].algorithm =
	data[hash].algorithm || OTPAlgorithm[OTPAlgorithm.SHA1];

The code after (in v8.0.0):

Authenticator/src/models/storage.ts

Lines 490 to 492 in 2cf9b0f

	algorithm: rawAlgorithm
	? (parseInt(rawAlgorithm) as OTPAlgorithm)
	: OTPAlgorithm.SHA1,

@mymindstorm parsed the algorithm-friendly name (SHA***) as an integer instead of casting the enum directly. This resulted in a NaN, which would be stripped during serialization.

Since SHA1 is now considered insecure, companies are likely using SHA256, which cannot be parsed and defaults to SHA1.

I wasn't sure if keeping undefined was what you wanted. Revert 1fc616b if you think it's better to always use SHA1 as the default.

It's the same parsing mistake for the type, but this one "worked" because the fallback was OTPType.totp (the most commonly used).

---

All of the following issues will likely be fixed by this pull request.

Fixes #1442
Fixes #1443
Fixes #1449
Fixes #1450

[blib]

@mymindstorm would you have a chance to look at this PR

[mymindstorm]

Hey, really appreciate this. I want to let y'all know that I am aware of the fixes piling up. I will try to get to merging and deploying, but am currently not at a point where I can commit enough time to do so.

[blib]

@mymindstorm thank you! looking forward to it. If there is anything that I can help you let me know!

[d-hansen]

@mymindstorm I get that you are extremely busy - many of us are.
However, in order for an open source project to remain viable within the community, it needs to continue to be maintained. Perhaps you could expand your pool of people that you trust and who are authorized to review and commit these necessary changes in your place.
Alternatively, someone else (or better several) needs to step up and become a new maintainer (presumably from a fork).
The current version has become minimally functional with a number of outstanding critical issues like this one. I'm sad about this because it is an awesome tool!