fix: feature digital credentials

[amanji]

Issue #: /bcgov/entity#18521

Description of changes:

• fixes discrepancy between queue message types.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the lear license (Apache 2.0).

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic High Entropy Secret	fd96a6e	legal-api/tests/unit/models/test_dc_definition.py	View secret
-	Generic High Entropy Secret	fc6c34a	legal-api/tests/unit/models/test_dc_definition.py	View secret
7220870	Generic High Entropy Secret	6beb1b1	legal-api/tests/unit/models/test_dc_definition.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
0.0% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[severinbeauvais]

Looks fine to me. Does it need to be deployed to Test?

[amanji]

Yes please. Just need to confirm it works there

[severinbeauvais]

What about the lint and test errors?

[severinbeauvais]

Akiff, at some point, can you use a fresh branch, or hard-reset it to main, so that the list of commits above goes away? :)

[severinbeauvais]

Yes please. Just need to confirm it works there

If Argus doesn't get to this by early afternoon, I will do it.

[argush3]

I agree with bc.registry.business.bn.

I think we should replace bc.registry.admin.manual with bc.registry.admin.revoke. My thought is we should still distinguish admin based operations. We'll need to update the cli to support this in some way.

[amanji]

Closing this as it has been addressed in #2330