Internal Timeout in GlobusExchangeTransport

[AK2000]

Summary

Previously, the GlobusExchangeTransport relied on waiting on receive indefinitely for a message. This causes problems when connections timeout (i.e. because of site of nginx policies). The ideal solution would be to move to SSE (#393) but this is blocked a bug within the globus_sdk. This PR is a temporary patch so that we can move forward with enforcing a maximum timeout in the cloud exchange (#390). This PR essentially allows the GlobusExchangeTransport to deal with timeouts gracefully.

Related Issues

• Closes Globus Exchange Client Causes Timeouts #391

Changes

• Breaking (backwards incompatible changes to public interfaces)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change or feature addition)
• Refactor (internal code or design clean up)
• Documentation (no changes to the code)
• Test (changes or additions to testing)
• Build (change to CI workflows or build processes)
• Package (changes to package metadata or dependency versions)

Testing

N/A

Pull Request Checklist

Please confirm the PR meets the following requirements.

• Relevant tags are added based on the types of changes.
• Code changes pass pre-commit (e.g., ruff, mypy, etc.).
• Tests have been added to show the fix is effective or that the new feature works.
• New and existing unit tests pass locally with the changes.
• Docs have been updated and reviewed if relevant.