Migrate cmdlets to centralized query-param handling

[juemerson-at-purestorage]

Follow-up to #32: bring the 176 straggler Get-* cmdlets in line with the 30 already migrated by #32 (PR #49), and refactor existing per-cmdlet mapping onto the shared helper. Consistency sweep — a uniform surface across the module.

• Refactor 156 cmdlets that already declare at least one of -Limit/-Sort/-Filter/-TotalOnly but hand-roll the $queryParams[...] mapping onto Add-PfbCommonQueryParams (includes Get-PfbHardwareTemperature, which declares -Limit but currently applies it client-side via Select-Object -First rather than as a query key)
• Add missing param declarations to 20 cmdlets that declare none of the four today (some are legitimately param-less singleton/config endpoints — verify each needs list-style params before adding)
• Cross-reference Reports/PfbApiDriftReport.md's Parameter Gaps table (39 relevant rows covering GET/Get-Pfb* limit/sort/filter/total_only gaps) for part of the missing-declaration work — it's a real but partial source, not exhaustive for the full 176
• Prioritize -Limit/-TotalOnly (real capability); -Sort/-Filter for uniformity
• Skip -TotalItemCount (net-new, 0 cmdlets today) unless a use case appears

Blocked on: #32 (centralized helper must exist first — see PR #49).
Owner: TBD.

[juemerson-at-purestorage]

Corrected the cmdlet counts and one factual claim above after an audit (2026-07-23), independently re-verified by a second pass before posting:

• 206 total Get-Pfb* cmdlets; 30 migrated by Centralize -Limit/-Sort/-Filter/-TotalOnly query-param handling in Invoke-PfbApiRequest #32 (PR Centralize -Filter/-Sort/-Limit/-TotalOnly query params (#32) #49, not yet merged); 176 remain in scope here.
• Of the 176: 155 already declare some/all of -Limit/-Sort/-Filter/-TotalOnly and hand-roll the query-key mapping directly (straightforward refactor onto Add-PfbCommonQueryParams); 20 declare none of the four at all (net-new param-declaration work — some of these may legitimately not need list-style params, e.g. singleton/config endpoints like Get-PfbDns, Get-PfbArray).
• Retracting an earlier claim in this thread that Reports/PfbApiDriftReport.md doesn't cover this gap — it does: its Parameter Gaps table has 39 rows matching a GET endpoint + Get-Pfb* cmdlet + a missing limit/sort/filter/total_only param (e.g. GET /active-directory → Get-PfbActiveDirectory → ids, limit, sort). It's a real, usable source for part of the missing-declaration work, just not exhaustive for the full 176 (most of the 155 already declare the param and hand-roll the mapping, so they don't show up there as "missing").

Methodology: AST-based param parsing plus regex/manual spot-checks, cross-verified by a second independent pass to rule out miscounts before publishing here.

[juemerson-at-purestorage]

One more correction: the refactor bucket is 156, not 155 (155 + 20 = 175, one short of the stated 176 total — an internal contradiction, caught while drafting the follow-up implementation plan). The discrepancy is Get-PfbHardwareTemperature: it declares -Limit, so it counts toward "declares ≥1 of the four" (156), but its current implementation applies the limit client-side via Select-Object -First rather than emitting a limit query key, which is why an earlier pass counted it out of the "hand-rolls a query key" bucket (155). It belongs in the refactor batch either way. Updated the checklist above accordingly.