🛠️ Description

Fixes #1996

In Set-BlobTriggerSubscription, the Add-AzDataFactoryV2TriggerSubscription call and the Get-AzDataFactoryV2TriggerSubscriptionStatus check were inside the same Invoke-WithRetry block. This caused the status to be checked immediately after subscribing (always Provisioning), and on retry the subscribe call would fail with Resource cannot be updated during provisioning, exhausting all retries.

Split into two steps:

1. The subscription operation wrapped in a try/catch that tolerates an already-transitioning subscription
2. A separate status-polling retry loop that waits for provisioning to complete

📋 Checklist

🔬 How did you test this change?

• 🤏 Lint tests
• 🤞 PS -WhatIf / az validate
• 👍 Manually deployed + verified
• 💪 Unit tests
• 🙌 Integration tests

🙋‍♀️ Do any of the following that apply?

• 🚨 This is a breaking change.
• 🤏 The change is less than 20 lines of code.

📑 Did you update docs/changelog.md?

• ✅ Updated changelog (required for dev PRs)
• ➡️ Will add log in a future PR (feature branch PRs only)
• ❎ Log not needed (small/internal change)

📖 Did you update documentation?

• ✅ Public docs in docs (required for dev)
• ✅ Public docs in docs-mslearn (required for dev)
• ✅ Internal dev docs in docs-wiki (required for dev)
• ✅ Internal dev docs in src (required for dev)
• ➡️ Will add docs in a future PR (feature branch PRs only)
• ❎ Docs not needed (small/internal change)