cast, cast5 and cast6 case

Rationale

<style type="text/css">br {mso-data-placement:same-cell;}</style> Aspect | CAST / CAST5 (CAST-128) | CAST6 (CAST-256) -- | -- | -- Block Size | 64 bits | 128 bits Key Sizes | 40–128 bits (variable) | 128–256 bits (fixed options) Rounds | 12 or 16 | 48 (12 quad-rounds) Structure | Classic Feistel network | Generalized Feistel network Primary Use | Legacy applications (e.g., PGP/GPG) | AES candidate; larger data security Security Notes | Adequate for its era but limited by small block size | Stronger against modern threats due to larger block and key options

Description

We need to address this case, which is related to #46 We have two options:

• we define the concept of family, which is wht CycloDX went for
• goven how popular these algorithms are and that there are only two variants, we add them both to the list

Action

• Discuss this case during a meeting and on this ticket
• Reach a consensus on how to proceed and document it on this ticket
• Create a PR

DoD

• Consensus reached
• Link to the description of the solution
• PR link
• PR merged

Start by reviewing the relationship to issue #46 and the two proposed approaches: defining an algorithm family or adding CAST and CAST6 separately. Discuss and document the consensus on this ticket, then create and link a PR; done means the decision, solution description, PR, and merge are recorded.