Centralize -Limit/-Sort/-Filter/-TotalOnly query-param handling in Invoke-PfbApiRequest

[juemerson-at-purestorage]

Common read query params (-Limit, -Sort, -Filter, -TotalOnly, plus -Name/-Id → names/ids) are mapped by hand in every cmdlet body (if ($Sort) { $q['sort'] = $Sort } …). ConvertTo-PfbQueryString only stringifies an already-built hashtable — there is no helper mapping $PSBoundParameters → the query hashtable.

• Add a shared helper (e.g. Add-PfbCommonQueryParams -BoundParameters $PSBoundParameters -Into $queryParams) encoding the standard name→key conventions
• Centralize -TotalOnly count-return handling (already partly in Invoke-PfbApiRequest)
• Document the convention so future cmdlets/generators use it

A user-facing parameter must still be declared in each cmdlet's param() block — this issue centralizes the behaviour/mapping, not the declarations (that sweep is the follow-up migration issue).

Per-parameter merit (roadmap): -Limit and -TotalOnly are load-bearing (auto-pagination means the pipeline cannot cap fetch); -Sort/-Filter are consistency-only. Consider landing the -Limit paginator fix in the same pass.

Blocked on: nothing.
Owner: Justin - fixed as PR #49

[juemerson-at-purestorage]

Implemented via PR #49 (#49), open, not yet merged.

Scope note for future readers: migration here was scoped by grepping for cmdlets that already declared -TotalOnly — that's the rarer, load-bearing param this issue was really about (per the roadmap note above), and its presence was a reliable signal a cmdlet had the complete four-param duplicate block this issue's example was describing. That grep found exactly 30 cmdlets; all 30 are migrated in #49.

This deliberately leaves out Get-Pfb* cmdlets that hand-roll -Filter/-Sort/-Limit but never had -TotalOnly declared — that's not a gap in this issue, it's -TotalOnly's absence putting them outside the grep by construction. That remaining set is tracked in #33, now corrected after an audit (independently re-verified) to 176 cmdlets: 155 already declare some/all of the four params and just need refactoring onto the shared helper, 20 declare none of the four and need net-new declarations (case-by-case, since some are legitimately param-less singleton/config endpoints). #33 also corrects an earlier claim in that thread that Reports/PfbApiDriftReport.md doesn't cover this category — it does, partially (39 relevant rows), see the discussion there.

[juemerson-at-purestorage]

Small correction to my comment above: the #33 split is 156 refactor / 20 net-new (176 total), not 155/20 — see #33 (comment) for why (one cmdlet, Get-PfbHardwareTemperature, declares -Limit but applies it client-side rather than as a query key, so it was miscounted out of the refactor bucket in the first pass).