Update V3Server support to account for non-NuGet.org repositories

[anamnavi]

PR Summary

Our existing V3 server support was supporting NuGet.org but not working for ADO server repositories. This PR changes the V3 server support to be more generalized to how all V3 servers should act (including ADO)

PR Context

Resolves #1054 #1000 #1149

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]

Okay, unfortunately I tested this against Artifactory and it's not yet working with those repositories just yet, but we may be small changes we need to make. No need to worry about that for this PR, I just wanted to see if this would handle Artifactory scenarios.