Add support for dependencies when publishing to ACR server

[alerickson]

PR Summary

This PR implements dependency support for publishing modules to ACR/container repositories.

This implementation attaches an artifact ("dependency") to the module being published that contains a file called dependency.json which lists all the first level dependencies for the parent package (retrieved from the module manifest of the module being published). The "dependency" artifact also has its own manifest (pictured below).

PR Context

Partially resolves #1516

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
  • [ ] None
  • OR
  • [x] [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.

[adityapatwardhan]

@alerickson - also need to add tests for this