Commit existing local Pester tests to /Tests/ for CI coverage

[juemerson-at-purestorage]

Some cmdlets/areas already have Pester test coverage that only exists locally — it was never committed to the repo. cross-platform-tests.yml (and any local Invoke-Pester run) can only execute what's under /Tests/, so this coverage isn't running anywhere in CI and isn't protecting against regressions.

• Gather whatever *.Tests.ps1 files exist locally/uncommitted for cmdlets already tested
• Rebase your local branch/working tree against current main first — several test files have landed there recently (query-param migration, capability-map work, etc.), so check for naming/fixture collisions before adding yours
• Verify each test still matches the cmdlet's current parameters/behavior — some of these cmdlets have changed since the tests were written, so confirm against main rather than assuming the local copy is still accurate
• Add them to /Tests/ following the existing <CmdletName>.Tests.ps1 naming convention (see current files there for examples)
• Confirm the full suite still passes via Invoke-Pester ./Tests before pushing
• Open a PR against main so cross-platform-tests.yml picks them up on the next push/PR

No production code changes required — this is pure test-asset migration. Cmdlets that don't have any test yet (local or committed) are out of scope here; that's a separate coverage-gap backlog item, not this issue.

Blocked on: nothing.
Owner: Don — has the local test files.