Fix mocking commands with [OrderedDictionary] parameters on PowerShell 7

[nohwnd]

Summary

Mocking a function that has a parameter typed [System.Collections.Specialized.OrderedDictionary] threw a ParseException on PowerShell 7, even though it worked on Windows PowerShell 5.1.

[System.Management.Automation.ProxyCommand]::GetParamBlock() — used to build the mock bootstrap function — serializes an OrderedDictionary parameter using the [ordered] type accelerator on PowerShell 7+. That accelerator is only valid as a cast on a hash literal ([ordered]@{}), not as a parameter type constraint, so the [scriptblock]::Create(...) that finalises the bootstrap function threw:

The ordered attribute can be specified only on a hash literal node.

before the test even ran. Windows PowerShell 5.1 emits the full type name instead, which is why it was unaffected.

Fix

Add a Repair-OrderedType helper (mirroring the existing Repair-EnumParameters) that rewrites the generated param-block, replacing the [ordered] / [ordered[]] accelerator in type-constraint position (the token immediately preceding ${ParameterName} for parameters the metadata reports as OrderedDictionary) with the full [System.Collections.Specialized.OrderedDictionary] type name. It is called right after Repair-EnumParameters. The match is bounded to the specific parameter variable so any legitimate [ordered]@{} cast is left untouched, and it early-returns when no [ordered] accelerator is present (e.g. on Windows PowerShell).

Tests

Added a regression Describe block in tst/functions/Mock.Tests.ps1 covering a scalar OrderedDictionary parameter, one mixed with other parameters, an OrderedDictionary[] array, and an end-to-end mock invoked through a wrapper with Should -Invoke. Confirmed these fail with the original ParseException before the fix and pass after it, on PowerShell 7.

Verification

• ./build.ps1 succeeds.
• ./test.ps1 -File tst/functions/Mock.Tests.ps1 -SkipPTests → 254 passed, 0 failed.
• Invoke-ScriptAnalyzer -Path ./src -Recurse -Settings ./.github/workflows/PSScriptAnalyzerSettings.psd1 → no new findings on the changed lines.

Fix #2370