[FEATURE]: Standard grouping (CBOM related)

There is a need to group cryptographic assets (possibly others) into a standard.

For example, the following can currently be represented:
- Use of a cryptographic algorithm for encryption (e.g. AES-256)
- Use of a cryptographic algorithm for signing (HS-256)
- Use of a `token` defined in relatedCryptoMaterial

What cannot be represented is the overall "standard" that these are part of. In this case JOSE. The current workaround is to leverage CycloneDX Properties.

Grouping these together into a standard would provide much more context into how these three seemingly independent components are used.

This was discussed in the [CycloneDX Cryptography Working Group call on 2025-08-07](https://www.youtube.com/watch?v=L-WgplNs_R8&list=PLqjEqUxHjy1WebDhYC_7-zDzGy8EqAqpP).

cc: @IanDeaks, @n1ckl0sk0rtge, @bhess