PR Summary

This change #10034 sets an empty string for the content which results in a content-length header with value 0. This was to fix a case where a web service doesn't accept explicit empty content for a put call. However, this broke a case with a get call where normally you don't send content and the server side is failing the request when we specify a content-length header with value 0.

So the change here is to only add the content-length header for empty content if it's not a get method call.

I was running the tests locally and the numerous progress bars being rendered created a different problem (hitting a debug assert), so to avoid that I suppressed all progress in the tests as it's not really used for the tests. Existing get test was modified to check that this header isn't being added.

Also had to update dotnet links so that static analysis passes as their old links no longer work.

PR Context

If you use:

invoke-restmethod https://api.npmjs.org/downloads/range/last-month/@microsoft/mgt

This fails with the server reporting a 500 (internal server error), but works with Windows PowerShell 5.1.

Fix #15186

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
  • Experimental feature(s) needed
    • Experimental feature name(s):
• 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 opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: