chore(release): 2.3.0

[dmann000]

2.3.0 release

Bumps ModuleVersion 2.2.0 → 2.3.0, adds the 2.3.0 CHANGELOG entry, and refreshes the manifest ReleaseNotes highlight.

Merge order — this PR goes LAST

It documents three PRs that are reviewed merge-ready and green but not yet merged. Land them first, then this:

• fix(replication): select array connections by remote_names, not the dead names query key #91 array-connection remote_names filter (fixes Dead names query key breaks -Name on five array-connection cmdlets and Update-PfbAsyncLog (unfiltered-PATCH risk falsified by live testing) #64) — breaking
• feat(core): report the HTTP status in API error messages #92 HTTP status in API error messages
• fix(replication): let RemoteDefaultExports suppress remote default exports (#55) #93 New-PfbFileSystemReplicaLink -RemoteDefaultExports suppression (refs New-PfbFilesystem: safe-by-default creation (no implicit exports, snapshot dir, or open SMB permissions) #55) — breaking

If any of those is held back, edit the CHANGELOG here before merging so it matches what actually shipped.

Breaking changes (also called out in the CHANGELOG)

• Update-PfbArrayConnection: -Name is now an alias of -RemoteName; supplying both together is a bind error.
• New-PfbFileSystemReplicaLink: -RemoteDefaultExports is now [Nullable[bool]]; the bare form needs a value.
• Update-PfbAsyncLog: -Name/-Id removed (endpoint has no selector).

Two breaking changes in a minor is consistent with repo practice (2.1.2 removed cmdlets), but if we'd rather signal them with a major, this becomes 3.0.0 — one-line change here.

After merge (maintainer)

1. Tag v2.3.0 and cut the GitHub release.
2. Gallery publish of the branded package (Publish-Gallery.ps1 reads this manifest version).
3. Re-sync the Pure org fork so customers pulling from it get 2.3.0.

Manifest verified to parse (Import-PowerShellDataFile → ModuleVersion 2.3.0).