Bugfix for ContainerRegistry repository Install-PSResource with varying digit version

[anamnavi]

Installing from a container registry repository should work even when the version the resource was published with is not the same as the normalized version, (i.e published version is 1.0, but normalized version is 1.0.0). The previous code was using the normalized version to query for the registry tag (version) and it wasn't an exact match. The exact tag is retrieved from the manifest and stored in PSResourceInfo.Version so use that for Install-PSResource.

For prerelease versions, when creating the normalized version string to write to the PSGetModuleInfo.xml file it was looking for versions with 3 or 4 digits, not accounting for 2 digits.

PR Summary

PR Context

Resolve #1623

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]

Can you add a note in the summary on the prerelease bug and fix for it as well?