ACR Integration: Populate metadata into PSResourceInfo object

[alerickson]

PR Summary

This PR takes the metadata json string stored in annotations and populates it into PSResourceInfo object. eg:

A small change was made to Publish-PSResource as well-- it now pushes org.opencontainers.image.title (the package name) and org.opencontainers.image.description (the full .nupkg name) to annotations. See documentation on naming conventions.

Note: the only way to retrieve annotations is to make a call to pull the manifest (ie GET request for a specific tag will not return layers, therefore will not return annotations). See: manifest response vs tag response

PR Context

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.