Update dotnet deps + run formatting on all relevant files + some fixes

[o-l-a-v]

This PR is just a suggestion on some housekeeping I think is due.

Feel free to close it or ask for changes.

PR Summary

• Copied settings for VSCode, EditorConfig and Markdownlint from PowerShell/PowerShell.
• Updated all dotnet deps with dotnet-outdated.
• Ran formatter on all relevant files with VSCode extension alexr00.formatallfilesinworkspace.
• Fixed missing dep in perf/benchmark.
• Use actual cmdlet Install-PSResource of PSResourceGet in setupReleaseTools, not the alias Install-Module.
• Don't hardcode path seperator char (/ vs \) in build scripts.

PR Context

Why?

• Keep syntax and style consistent with PowerShell/PowerShell, for both C#, PowerShell and Markdown.
• Run formatter on all relevant files, so that future PRs that fixes one thing does not show that the whole file changed due to running the formatter.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[alerickson]

It looks like the build isn't working in CI for this PR

[o-l-a-v]

It builds fine on my Windows machine. 🤔

---

Seems GitHub actions builds on Ubuntu 22.04.

• https://github.com/PowerShell/PSResourceGet/actions/runs/16298810166/job/46027714439?pr=1846

Can it (Linux) even target net472?

---

Why the Windows Server 2022 build fails I don't know.

• https://dev.azure.com/powershell/PowerShellGet/_build/results?buildId=156008&view=logs&j=8b1bcd32-f438-5921-a69d-92ff85a481b1&t=1864767e-a38d-545a-f243-ec8cd3c81abd

[alerickson]

It builds fine on my (Windows) machine as well, but I just pulled in your most recent changes and it's (still) not building on the server. We only build on windows, and then we use that build to test Windows PowerShell on Windows and PowerShell Core on Windows, Mac and Ubuntu.

Could you try opening up a new PR with a subset of these changes? It may help to have a smaller set of changes

[o-l-a-v]

Could we get more output on what/where it fails? dotnet.exe will create log files, right?

[alerickson]

@adityapatwardhan's change resolved the build issue (just an incorrect file name), but it looks like many of the tests are failing with the same error:

Error parsing server metadata: Could not load file or assembly
| 'System.IO.Pipelines, Version=9.0.0.6, Culture=neutral,
| PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file
| specified.