feat(registry): add HPKE (RFC 9180) to Cryptography Registry

[Mehrn0ush]

As discussed in ticket #765, this PR adds HPKE (RFC 9180) to the Cryptography Registry.

Fixes #765

Details

• Adds the HPKE algorithm family with pattern HPKE[-{mode}]-{kem}-{kdf}-{aead} (primitive: pke).
• Adds RFC 9180 as the authoritative reference.
• Updates the registry schema enum to allow HPKE.

Scope

• Registry-only (schema/cryptography-defs.json) plus corresponding registry schema update (schema/cryptography-defs.schema.json).
• No CycloneDX specification behavior changes.

[stevespringett]

@bhess

[bhess]

Thanks for this addition of HPKE. Please see the one comment inline. Other than that, LGTM!

[bhess]

Since the modes are well-defined by the RFC, I'd suggest the following pattern:
HPKE[-(mode_base|mode_psk|mode_auth|mode_auth_psk)]-{kem}-{kdf}-{aead}

[Copilot]

Pull request overview

This PR adds HPKE (Hybrid Public Key Encryption from RFC 9180) to the Cryptography Registry. The addition follows the existing pattern for algorithm families and adds HPKE between ECIES and MQV in alphabetical order.

Changes:

• Adds HPKE algorithm family entry with RFC 9180 as the authoritative reference
• Defines the pattern HPKE[-{mode}]-{kem}-{kdf}-{aead} with primitive type pke
• Maintains alphabetical ordering of algorithm families

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

There is trailing whitespace after the closing brace and comma. This should be removed to maintain consistent formatting.

Suggested change

	},
	},

[Copilot]

The RFC name should be "RFC9180" without a space to maintain consistency with the predominant naming pattern used in this file. Most RFC entries use the format "RFCnnnn" without a space, such as "RFC8017", "RFC8032", "RFC7919", "RFC5869", etc.

Suggested change

	"name": "RFC 9180",
	"name": "RFC9180",

[stevespringett]

Update the pattern to match what @bhess had suggested