ACR Integration: Bug fix for publishing a module that is not all lowercase to ACR repo

[alerickson]

PR Summary

This PR addresses a small bug when publishing to ACR registries. ACR only allows all lowercase names. This PR takes all module names and ensures that it's lowercase when publishing to ACR. It does not modify the files or .nupkg, just the name that gets sent in the HTTP calls to ACR.

PR Context

Previously, when attempting to publish 'TestModule.psd1' a 404 error would be returned. The exact same file named 'testmodule.psd1' would successfully publish. This is because the Publish-PSResource implementation gets the module name from the file _pkgName = System.IO.Path.GetFileNameWithoutExtension(pathToFileToPublish). However, ACR does not care about the casing of the file or the .nupkg, just the metadata it receives.

PR Checklist

• [x] PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• [x] Summarized changes
• [x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• [x] 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
  • [x] None
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• User-facing changes
  • [x] Not Applicable
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• Testing - New and feature
  • [x] 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
  • [x] 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.