feat(rust/rbac-registration): refactoring

[stanislav-tkach]

Description

• The Cip0134UriSet type was added.
• Option<Vec<_>> fields of the Cip509RbacMetadata structure were changed to Vec<_>.
• Error handling becomes stricter.
• Store x509 certificates (Cip509RbacMetadata::x509_certs) in the decoded format.
• Store certificate URIs in the registration chain.

Related Issue(s)

Closes #104.

Related Pull Requests

This is a combination of the following pull requests:

• feat(rust/rbac-registration): Introduce Cip0134UriSet type #119
• feat(rust/rbac-registration): Store decoded x509 certificates #128
• feat(rust/rbac-registration): Store and update certificate URIs in the registration chain #130

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 230/230}$ | ${\color{red}Fail: 0/230}$ |

[bkioshn]

LGTM 🌈

[stevenj]

The metadata should take the paired transaction and witness set as context. Its not possible to decode properly without it, i don't think?

[bkioshn]

It is needed in validation and collecting the data for the registration chain.

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 256/256}$ | ${\color{red}Fail: 0/256}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 256/256}$ | ${\color{red}Fail: 0/256}$ |