Add support for ACR when publishing scripts

[anamnavi]

PR Summary

Add support for scripts for ACR, for publish and install.
Add tests for scripts for publish.
Fix bug where ACR expects lowercase name but user provided input doesn't match it.

Still to do:
fix bug where there's a mismatch between actual version (that ends with 0) and user provided version that may have more or less versions.
Also versions cannot be expected to be in any order, they are only in order of when they were published. Fix this bug too.
PSResourceInfo.Type property will still reflect none when Find-PSResource or Get-InstalledPSResource is called for ACR resources. This will be fixed after cleanup refactor.

PR Context

Resolves #1578 #1568

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]

Looks good, just add a test or add a validation in an existing test.

[alerickson]

resolves #1578