fix(powershell): replace UrlEncode with System.Uri EscapeDataString for path parameter encoding

[Mattias-Sehlstedt]

Path parameters are currently encoded with UrlEncode, but in the documentation there is a remark for how it will handle spaces, and it suggests to instead use UrlPathEncode.

Edit: The solution has been adjusted to using System.Uri and EscapeDataString based on feedback. This since UrlPathEncode is designed for full path construction and not the path-by-path template building that is occurring in code.

Could be considered a breaking change if someone relies on a space being encoded as + rather than the usual %20. The current behavior comes from #9688.

Fixes: #24602

PR checklist

• Read the contribution guidelines.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

---

Summary by cubic

Corrected path parameter encoding in PowerShell clients so spaces encode as %20 and “+” is no longer used. Replaced UrlEncode with [System.Uri]::EscapeDataString to follow .NET guidance (fixes #24602).

• Bug Fixes

  • Update PowerShell api.mustache to encode path params with [System.Uri]::EscapeDataString([string]$param).
  • Add a test to verify escaping in generated scripts; regenerate samples.

• Migration

  • Spaces in path params now encode as %20 instead of +. Update expectations or pin the previous generator version.

^{Written for commit 60588c8. Summary will update on new commits.}

[Mattias-Sehlstedt]

@FeckNeck could you try changing the api.mustache locally and verifying that this solves your issue?

[cubic-dev-ai]

All reported issues were addressed across 6 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 6 files

_{Re-trigger cubic}

[cubic-dev-ai]

No issues found across 6 files

_{Re-trigger cubic}

[FeckNeck]

@FeckNeck could you try changing the api.mustache locally and verifying that this solves your issue?

Sorry for the late reply. I'm still quite new to OpenAPI Generator, actually.
Could you please clarify exactly what you'd like me to do ?
Anyways, I tested by replacing UrlEncode with System.Uri EscapeDataString and it's working as intented.
Thank you very much for the PR !