fix: use pre-3.10 type annotations for compatibility

[JAVGan]

Summary

• Replace PEP 604 union syntax (bytes | None) with Optional[bytes] in tests/ms_azure/test_session.py
• Replace builtin generic types (tuple[], type[]) with typing equivalents (Tuple, Type) for Python < 3.10 compatibility

Refers to SPSTRAT-731

Test plan

• Verify tests pass on Python 3.9

🤖 Generated with Claude Code

Summary by Sourcery

Update Azure session tests to use pre-3.10 compatible type annotations.

Enhancements:

• Align type hints in Azure session tests with typing module generics for Python versions prior to 3.10.

Tests:

• Adjust type annotations in Azure session test helpers to maintain compatibility with Python 3.9.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts type annotations in Azure session tests to use pre-3.10 typing syntax for compatibility with Python 3.9 and earlier.

File-Level Changes

Change	Details	Files
Update helper function signatures to use typing.Type and typing.Tuple instead of builtin generics for Python < 3.10 compatibility.	Change handler parameter annotation from builtin type[...] to typing.Type[...] in _start_local_server Change return type annotation from builtin tuple[...] to typing.Tuple[...] in _start_local_server Change return type annotation from builtin tuple[...] to typing.Tuple[...] in _sequential_http_handler	tests/ms_azure/test_session.py
Replace PEP 604 union syntax with Optional[...] for compatibility with older Python versions.	Update responses element type from bytes	None to Optional[bytes] in _sequential_http_handler parameter annotation

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[lslebodn]

If we want to support 3.9 tahn we shdoul also test it :-)

Shall we revert f922a43

[JAVGan]

If we want to support 3.9 tahn we shdoul also test it :-)

Shall we revert f922a43

#201

I'll open one for starmap-client as well

[JAVGan]

@lslebodn is it ok to just change the annotations and keep 3.9 dropped?

I can then update CLAUDE.md in the #198 to mention the way we use to annotate typing as the same standard.

It won't solve 3.9 issues but we'll be more consistent.

I'll also close #201 since it will be a mess to add back an EOL version

[lslebodn]

from __future__ import annotations should help to keep simplified syntax introduced in https://peps.python.org/pep-0604/.

Cause it makes all annotations strings (PEP 563 deferred evaluation) rather than
evaluating them eagerly. But I would prefer to have deferred just in 3.9

And we should test it with python3.9 anyway.