feat(jwt): Improve JWT expiration handling and fix naming conflicts

• Replacedtime.time() withdatetime.datetime.utcnow() to ensure accurate expiration handling.
• Useddatetime.timedelta(seconds=...) for better timestamp calculations.
• Ensured compatibility withjwt.encode() by converting expiration times using.timestamp().
• Renamedalgorithm tojwt_algorithm to avoid conflicts with theALGORITHM constant and ensure consistency.

test(twilio): Add unit test for Twilio Video Room creation

• Integratedunittest framework for structured testing.
• Usedresponses library to mock Twilio API calls.
• Implemented a test case that validates room creation by checkingsid,unique_name, andstatus.

These changes enhance JWT handling, resolve potential naming conflicts, and introduce automated testing for Twilio API interactions.

Fixes#777

Summary of Changes

This PR addresses the following improvements:

• Fix for IssueCode Enhancement #777 (JWT Expiration Handling):

  • Replacedtime.time() withdatetime.datetime.utcnow() to ensure accurate expiration calculations.
  • Applieddatetime.timedelta(seconds=...) to improve timestamp consistency.
  • Ensured compatibility withjwt.encode() by converting expiration times using.timestamp().
  • These changes improve time handling accuracy, ensuring JWTs expire correctly across different time zones.

• Resolved SonarCloud issue (Naming Conflict with ALGORITHM):

  • Renamedalgorithm parameter tojwt_algorithm to prevent confusion with theALGORITHM constant.
  • This improves maintainability by avoiding case-sensitive conflicts in variable names.

• Added a new unit test for Twilio Video Room creation:

  • Integratedunittest framework for structured testing.
  • Mocked Twilio API calls using theresponses library.
  • Verified room creation by checkingsid,unique_name, andstatus.
  • Note: Existing tests already cover the JWT expiration fix, so no additional tests were needed for that.

Checklist

• I acknowledge that all my contributions will be made under the project's license.
• I have made a material change to the repo (functionality, testing, spelling, grammar).
• I have read theContribution Guidelines and my PR follows them.
• I have titled the PR appropriately.
• I have updated my branch with the main branch.
• I have added inline documentation to the code I modified.
• I have added tests that prove my fix is effective or that my feature works (not required, as existing tests already cover the fix).
• I have added the necessary documentation about the functionality in the appropriate.md file (not required).

If you have questions, please file asupport ticket, or create a GitHub Issue in this repository.