Cap microsoft-kiota-http below 1.13 in the Microsoft Azure provider

[dabla]

microsoft-kiota-http 1.13.0 moved the per-request options from request.options to request.extensions. msgraph-core 1.5.1, the latest release, still only runs the middleware pipeline of AsyncGraphTransport when hasattr(request, "options"). With microsoft-kiota-http 1.13 or later, every request made through KiotaRequestAdapterHook therefore skips the redirect, retry, URL replacement and user agent handlers:

• a drive item download (/content answers 302) returns Graph's raw redirect with an empty body, so run(..., response_type="bytes") returns None;
• 429 and 503 are no longer retried.

The current constraints-3-3 (1.14.0) and constraints-main (1.14.1) both resolve to an affected version. 1.14.1 is affected too.

This caps microsoft-kiota-http<1.13.0 until a msgraph-core release reads request.extensions. The fix is in review in microsoftgraph/msgraph-sdk-python-core#1129, for microsoftgraph/msgraph-sdk-python-core#1128. The cap carries a comment linking both issues. uv.lock only changes the microsoft-kiota-http entry (1.14.0 → 1.12.3).

Verified with Kiota's real HttpxRequestAdapter against an httpx.MockTransport answering 302 then the file: microsoft-kiota-http 1.12.3 returns the bytes, while 1.14.0 and 1.14.1 return None. That holds with microsoft-kiota-abstractions 1.14.0, so only microsoft-kiota-http needs the cap. The provider's msgraph hook, operator and sensor tests pass on 1.12.3.

closes: #74089

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Opus 5.5

Generated-by: Claude Opus 5.5 following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.