Fix Azure Data Factory hook broken with azure-mgmt-datafactory 10

[FrankYang0529]

Why

• The CI dependency upgrade PR ([main] Upgrade important CI environment #69694) bumps azure-mgmt-datafactory 9.3.0 → 10.0.0, which replaced the if_match/if_none_match parameters with etag + match_condition pair.
  • https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/datafactory/azure-mgmt-datafactory/CHANGELOG.md#breaking-changes

How

• Use azure.mgmt.datafactory version to determine kwargs: _ADF_SDK_V10_PLUS is computed from the installed major and the hook's public if_match/if_none_match parameters are translated accordingly.
  • The v10+ sends etag + match_condition.
  • Older SDKs keep the original if_match/if_none_match kwargs.

Verification

• uv run --project providers/microsoft/azure --with "azure-mgmt-datafactory==9.3.0" pytest providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_data_factory.py -q
• uv run --project providers/microsoft/azure --with "azure-mgmt-datafactory==10.0.0" pytest providers/microsoft/azure/tests/unit/microsoft/azure/hooks/test_data_factory.py -q

---

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

• Yes - Claude Code

---

• 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.

[Lee-W]

@eladkal I like this, but I'm not sure we've done something like this before. Increasing the minimum supported version from 2 to 10 seems a bit aggressive, so I suggested keeping it backward compatible.

[eladkal]

Temporary block till I take a closer look

[eladkal]

OK, I reviewed the case and I think it's OK to support azure-mgmt-datafactory>=10 only.
I rather avoid overcomplicating the code unless we have clear indication that it's worth it.

The azure-mgmt-datafactory releases are not that frequent which is why we kept supporting old versions of it. Users of older versions can just use one version behind of the provider - should be perfectly fine.

@FrankYang0529 can you please adjust the code for that?

[FrankYang0529]

Thanks for the review. I will update it today.

[FrankYang0529]

Updated it. Thank you.

Elad approve by comment.

[jason810496]

OK, I reviewed the case and I think it's OK to support azure-mgmt-datafactory>=10 only.

Merging then, thanks.