Add FOCUS 1.3 hub functions (HubSetup_v1_3.kql)

[flanakin]

Summary

Phase 2 of FOCUS 1.4 work (parent: #2120). Adds the hub-side FOCUS 1.3 functions and retargets the unversioned aliases.

Stacked on phase 1 (#2126). Once phase 1 merges to `flanakin/focus14`, this PR's base is automatically retargeted by GitHub.

Files

• NEW: `HubSetup_v1_3.kql` (619 lines, copied from v1_2 with renames + FOCUS 1.3 column adds + new v1_2 union arm)
• MODIFIED: `HubSetup_Latest.kql` — aliases now point to `_v1_3()` instead of `_v1_2()`
• MODIFIED: `app.bicep` and `.build.config` — wires `HubSetup_v1_3.kql` into the deployment

Functions added

• `Costs_v1_3()` — unions `Costs_final_v1_3`, `Costs_final_v1_2` (with 1.3 column extends), and `Costs_final_v1_0` (with v1_0→v1_2 conversion + 1.3 column extends).
• `Prices_v1_3()`, `CommitmentDiscountUsage_v1_3()`, `Recommendations_v1_3()`, `Transactions_v1_3()` — schema-equivalent to v1_2 (no FOCUS 1.3 changes for these datasets), renamed for consistency with the version family.

Backward compatibility

For v1_2 data unioned through `Costs_v1_3()`:

• 8 new FOCUS 1.3 columns default to null/empty (`AllocatedMethodId/Details/ResourceId/ResourceName/Tags`, `ContractApplied`).
• `ServiceProviderName` populated from `ProviderName`.
• `HostProviderName` populated from `PublisherName`.

What's NOT in this PR

• Contract Commitment hub function (phase 3, separate dataset).
• FOCUS 1.4 (phases 4-5).

Closes #2127

Test plan

• Pester unit tests pass: 192/192 in HubsIngestionQueries.Tests.ps1
• Bicep template compiles cleanly
• Manual smoke test: deploy hub, query `Costs()` and confirm v1_3 schema (8 new columns visible).
• Manual smoke test: query `Costs_v1_2()` after deploying v1_3 — confirm v1_2 schema still returned.