Patch for cases where the bearer token has no expiration

[ponyisi]

Code assumed an "exp" field was available in JWT bearer tokens. While this is good practice it is not mandatory. Handle this edge case.

[Copilot]

Pull Request Overview

This PR addresses the edge case where JWT bearer tokens may not include an expiration ("exp") field by introducing a new helper function and updating token expiration checks. Key changes include:

• Adding a static method _effective_expiration to handle tokens without an exp field.
• Updating token expiration comparisons in _get_authorization to use the new helper.
• Modifying the test to use patch.dict for environment variable setup, eliminating the need for manual cleanup.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
tests/test_servicex_adapter.py	Replaces manual BEARER_TOKEN_FILE setup/teardown with a patch.dict context manager
servicex/servicex_adapter.py	Introduces _effective_expiration to handle missing token expiration and updates usage

Comments suppressed due to low confidence (1)

servicex/servicex_adapter.py:89

• [nitpick] Consider renaming the parameter 'tok' to 'token' for better clarity, and adding a docstring to explain the function's purpose and behavior.

def _effective_expiration(tok) -> float: