[DevOps] PR Builds: Add deployment checkboxes to PR template

[flanakin]

🛠️ Description

Adds a "Deploy to test?" section to the PR template with checkboxes for CI-driven deployments:

• Hubs with ADX (managed) — ADX + managed exports, data available in ~24hrs
• Hubs with Fabric (manual) — Fabric eventhouse + manual exports
• Hubs (manual) — Storage-only + manual exports
• Hubs (no data) — Storage-only, no exports (fastest)
• Workbooks — Workbook template
• Alerts — Alerts template

These checkboxes will be parsed by the upcoming ftk-pr-deploy workflow to determine which deployments to run per PR.

This is PR B of a multi-PR effort to add per-PR deployment CI for FinOps hubs.

📋 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)

[Copilot]

Pull request overview

Updates the GitHub pull request template to let authors indicate which CI-driven “deploy to test” scenarios should run for a given PR, supporting upcoming per-PR deployment automation for FinOps hubs.

Changes:

• Adds a new “Deploy to test?” checklist section to the PR template.
• Introduces deployment option checkboxes for hubs variants, workbooks, and alerts.

Comments suppressed due to low confidence (1)

.github/PULL_REQUEST_TEMPLATE.md:32

• Because these checkboxes are intended to be parsed by the upcoming ftk-pr-deploy workflow, the option text should be as stable and machine-friendly as possible. The inline HTML comment on the “Hubs with Fabric (manual) — URI:” line (and the variable URI content itself) can make parsing brittle; consider keeping the checkbox label fixed and moving URI instructions/input to a separate line (or using a hidden, immutable token/ID that the workflow parses).

> - [ ] Hubs with ADX (managed)
> - [ ] Hubs with Fabric (manual) — URI: <!-- paste eventhouse query URI -->
> - [ ] Hubs (manual)