Re-record 8 stale functional test playback recordings (pre-existing)

Eight functional test cassette recordings are stale on `main` and fail when replayed. They've been silently excluded from `mage preflight` playback coverage via `excludedPlaybackTests` in `cli/azd/magefile.go`, which masks unrelated regressions. Per PR #7776 review, this issue tracks re-recording them so the exclusion list can stay minimal (only genuinely WIP-branch-affected recordings).

**Tests to re-record:**

1. `Test_CLI_PreflightQuota_Sub_DefaultCapacity`
2. `Test_CLI_PreflightQuota_Sub_DifferentLocation`
3. `Test_CLI_PreflightQuota_Sub_InvalidModelName`
4. `Test_CLI_PreflightQuota_RG_DefaultCapacity`
5. `Test_CLI_PreflightQuota_RG_InvalidModelName`
6. `Test_CLI_PreflightQuota_RG_InvalidVersion`
7. `Test_CLI_Deploy_SlotDeployment`
8. `Test_CLI_VsServer`

**Re-record procedure:**

```sh
cd cli/azd
AZURE_RECORD_MODE=live go test ./test/functional -run "^Test_CLI_PreflightQuota_Sub_DefaultCapacity$" -count=1 -timeout 30m
# (repeat per test, commit new YAML recordings under test/functional/testdata/recordings/)
```

**Context:**

- Each failure is a cassette/replay mismatch, not a real product bug.
- They live in `cli/azd/test/functional/testdata/recordings/`.
- Because preflight's playback step is advisory (non-blocking warn), removing them from `excludedPlaybackTests` in PR #7776 surfaces the failures as warnings but does not block the gate.
- The remaining `excludedPlaybackTests` entries in PR #7776 are for recordings affected by the graph-driven provision path and will be re-recorded as part of that PR's merge steps.

/cc @wbreza