[AAP-38778] chore: improve jwt expired exception logging

[Dostonbek1]

[AAP-38778] Improve JWT expired exception logging

Description

• What is being changed?
  Add more meaningful log message when jwt token is expired.
• Why is this change needed?
  To make it easier for customers/developers to understand the root cause of authentication errors.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test update
• Refactoring (no functional changes)
• Development environment change
• Configuration change

Self-Review Checklist

• I have performed a self-review of my code
• I have added relevant comments to complex code sections
• I have updated documentation where needed
• I have considered the security impact of these changes
• I have considered performance implications
• I have thought about error handling and edge cases
• I have tested the changes in my local environment

Testing Instructions

Prerequisites

Steps to Test

Expected Results

Additional Context

Required Actions

• Requires documentation updates
• Requires downstream repository changes
• Requires infrastructure/deployment changes
• Requires coordination with other teams
• Blocked by PR/MR: #XXX

Screenshots/Logs

[john-westcott-iv]

@Dostonbek1 please let us know if you need reviews once the tests are all fixed.

[kdelee]

Having this error in way that is exposed to end user is big improvement/should reduce time to diagnoses of the root cause. We still need to do some work in aapqa-provisioner to provision nodes w/ clocks in sync and MAYBE consider if installer should check this.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud