Cut 5098 sdk filter updates

[jworkmanjc]

Issues

• CUT-5098 - SDK QueryFilter Update

What does this solve?

Some change in our V2 API resulted in queryFilter URLs like: https://console.jumpcloud.com/api/v2/systeminsights/users?filter[0]=system_id:eq:69835d723217d75a74edeec1&skip=0&limit=100 to no longer be supported.

This release addresses this issue by removing the number index in queryFilters and instead just writing queryFilter strings like: filter=something:eq:this&filter=somethingelse:eq:that

Both the V1 and V2 SDKs support this type filtering so now they should be similar in how multiple (or even single) filters are applied.

Is there anything particularly tricky?

How should this be tested?

Screenshots

---

Note

Medium Risk
Changes how Filter arrays are serialized into query strings for generated V1/V2 clients, which can affect request semantics and potentially break consumers relying on the previous filter[index]=... format. Remaining changes are version bumps and generated metadata/format updates with low functional risk.

Overview
Updates the PowerShell SDK build pipeline to rewrite AutoRest-generated C# so multi-value Filter parameters are sent as repeated query keys (filter=...&filter=...) instead of indexed keys, aligning V1 and V2 behavior and addressing recent V2 API incompatibility.

Improves BuildCustomFunctions.ps1 robustness by capturing npx autorest --version output even when AutoRest exits non-zero due to deprecation notices. Bumps module versions (V1 to 0.1.3, V2 to 0.2.1) and updates release notes plus regenerated V1 packaging/format metadata (manifest/nuspec/csproj and *.format.ps1xml view changes).

^{Written by Cursor Bugbot for commit 58b35ec. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[gweinjc]

Changes look good to me