feat: w3c revocation using bit string status list for dedicated and multi-tenancy

[KulkarniShashank]

What

• Implemented W3C credential revocation using a bit string status list.
• Added support for both dedicated and multi-tenancy scenarios.
• Integrated with the existing credential status management system.

Why

• To enable the revocation of W3C credentials in compliance with the standard.
• To support various deployment configurations, including multi-tenant environments, enhancing the flexibility and scalability of the solution.

How

• Created new functions for generating, encoding, and decoding bit string status lists.
• Integrated these functions into the credential issuance and verification processes.
• Extended the credential management logic to handle revocation checks for both dedicated and multi-tenant environments.
• Updated existing modules to support the new revocation features, ensuring backward compatibility.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[GHkrishna]

Converting to draft as revocation support for w3c will be implemented after merge of w3c revocation support in credo-ts with PR #2024 in credo-ts

[sairanjit]

This will be closed after the #262 is completed