Monorepo: Expand support for deploying multiple app configurations within the same workspace project

[MicroFish91]

I. Overview

At the current time we only support saving & deploying from one workspace app configuration. To support saving and deploying from multiple app configurations, we need to migrate to a new schema and add additional capabilities as shown below.

II. Flow

III. Schema

Old:

New:

IV. Work Items

Deploy Project from Workspace (internal):

• Add support for taking an existing envPath and converting it to environment variables on the CA envelope
• Update the settings save logic to abide by the new schema
• Update default resource naming logic
• Decouple settings validation and parsing logic from deployWorkspaceProjectInternal

Monorepo:

• Add hover descriptions for the new json schemas
• Add ability to detect and convert old schema to new schema (In Review)
• Monorepo core logic
  See linked issue for additional task breakdown.
• Telemetry

Finishing touches (added 3/26):

• Better default naming convention for each resource (e.g. -rg, -me, -ca)
• Try to default container registry when a tree item is provided
• Also try to default a container registry within the internal logic if one still hasn't been provided
• Don't show a dropdown for loading workspace configuration in activity log if no children provided
• Flat-list all the activity log items for the resource verification steps
• Provide a good test repo for CTI
• Engineering: Revisit/document step priority levels in a way that makes sense

Dilithium:

• Tests

TBD:

• Reconfiguring existing settings before deployment
• More streamlined path for existing container app project integration
• Update the activity log API to accept an option indicating whether to auto-expand a top-level activity node without user input and utilize in the deployment configuration logic for monorepo