fix: traction auth decorator

[amanji]

Issue #: /bcgov/entity#18578

Description of changes:

• Improves token validation in the Traction auth decorator.
  • Previously, tokens were decoded without validating the expiration date. This resulted in the token being perceived as valid when it should have been refreshed.
  • This PR adds that additional logic to fix 401 errors returning from Traction/ACA-Py

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>

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[codecov]

Codecov Report

Merging #2308 (cb4945e) into main (79511cd) will decrease coverage by 1.00%.
Report is 22 commits behind head on main.
The diff coverage is 49.14%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2308      +/-   ##
==========================================
- Coverage   77.37%   76.38%   -1.00%     
==========================================
  Files         202      163      -39     
  Lines       11602    10103    -1499     
  Branches     1961     1698     -263     
==========================================
- Hits         8977     7717    -1260     
+ Misses       2043     1922     -121     
+ Partials      582      464     -118     

Flag	Coverage Δ
entityfiler	?
legalapi	76.38% <49.14%> (-0.46%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
legal-api/src/legal_api/config.py	95.16% <100.00%> (+0.28%)	⬆️
legal-api/src/legal_api/core/filing.py	86.55% <ø> (+0.04%)	⬆️
legal-api/src/legal_api/core/meta/filing.py	91.11% <ø> (ø)
legal-api/src/legal_api/models/__init__.py	100.00% <100.00%> (ø)
legal-api/src/legal_api/models/dc_definition.py	90.69% <100.00%> (ø)
...gal_api/services/filings/validations/alteration.py	83.01% <100.00%> (ø)
legal-api/src/legal_api/version.py	100.00% <100.00%> (ø)
...l_api/models/dc_issued_business_user_credential.py	94.44% <94.44%> (ø)
legal-api/src/legal_api/models/dc_connection.py	87.50% <33.33%> (-1.39%)	⬇️
...egal-api/src/legal_api/resources/v2/namerequest.py	28.57% <0.00%> (ø)
... and 5 more

... and 44 files with indirect coverage changes