fix: make algorithm type enum compatible with GraphQL

[taleodor]

No description provided.

[ppkarwasz]

There are at least four standards relevant to TEA that define checksum algorithm names, each with its own conventions:

• CycloneDX
• SPDX 2.x
• SPDX 3.x
• Package URL (purl)

These standards differ in more than just casing—they use different separators and naming conventions. For example, the SHA-1 algorithm appears as SHA-1, SHA1, and even sha1 depending on the context.

Ideally, we should aim for consistency across formats, but it’s not clear which convention to standardize on. One option might be to align with the IANA registry of named information, which provides a more neutral and centrally managed way to assign names.

If we do decide to normalize algorithm names, we could apply a simple, deterministic transformation to the IANA names, such as:

• Converting all characters to uppercase
• Replacing hyphens (-) with underscores (_)

[ppkarwasz]

All enum constants follow a common <algorithm_name>[_<output_size>] pattern, where the <algorithm_name> is composed of alphanumeric characters only. SHA_1 is the exception, so I would suggest to rename it to SHA1.

[taleodor]

Thank you, renamed.

Regarding,

• Converting all characters to uppercase
• Replacing hyphens (-) with underscores (_)
  -> This is essentially GraphQL's convention for enums - https://graphql.com/learn/enums/

[ppkarwasz]

Not only GraphQL does not allow hyphens in enum names! 😉

Your changes might simplify the life of many implementors! 💯