[AA4AM] Add deployment settings generator to Solution Export Pipeline

[mikefactorial]

Is your feature request related to a problem? Please describe.
Currently deployment settings json files for AA4AM have to be generated manually. We should be able to partially automate this work.

Describe the solution you'd like

UPDATE: Instead of generating deployment settings from the CoE CLI we will generate the deployment settings from the export pipeline so anytime a solution is exported to source control the deployment settings are generated / updated.
Ideally, we would be able to point the CoE CLI at an environment (e.g. Dev) and generate the json structure for the deploymentSettings.json and customDeploymentSettings.json as a first step to automate this. It would then be the responsibility of the user to set the values in the settings json. When PAC CLI has this feature available for ConnectionReferences and EnvironmentVariables we should wrap the PAC CLI commands to generate the deploymentSettings.json. We will then need to generate the other settings that would live in the customDeploymentSettings.json (e.g. SolutionComponentOwnershipConfiguration, AadGroupTeamConfiguration, AadGroupCanvasConfiguration) which are specific
to the AA4AM pipelines and not planned currently to be part of PAC CLI or build tools at this time.

A second step would be to automate setting the values in the json files as well as the structure by pointing at a second environment (e.g. Test, Validation, Prod) and looking for specific connection references, teams (aad groups) etc. and setting the values in the settings json. This will require some additional work to rationalize since some of the values may not be able to simply discern without the user's input (e.g. what AAD Group or what the environment variable values should be).

Describe alternatives you've considered
We could instruct users to run both PAC CLI to generate deploymentSettings.json and also run CoE CLI to generate customDeploymentSettings.json but the user experience would be cleaner if we wrap PAC CLI and have both files generated with a single command in CoE CLI.

Additional context
https://github.com/microsoft/coe-starter-kit/blob/ALMAcceleratorForAdvancedMakers/ALMAcceleratorForAdvancedMakers/DEPLOYMENTCONFIGGUIDE.md

[mikefactorial]

One note on this is we'll need to ensure that we can regenerate the deployment configuration files anytime an update is made to a solution (e.g. New Connection Reference Added, New Environment Variable, New App etc.) without losing the existing configuration.

[Grant-Archibald-MS]

@mikefactorial, Sounds good will need to align with the configuration file generated by the coe aa4am generate install aa4am.schema.json.

Maybe add a new command coe aa4am generate solution config -o https://dev.azure.com/contoso -p alm-sandbox -f solution.config

(Could be similar to coe aa4am generate install that creates config file to coe aa4am install)

The settings should be able to read from Azure DevOps to generate the files e.g.

• Service Connections can generate the ConnectionReferences
• Environment Variables from Variable Group / Build Pipeline Variables
• Canvas Application / Sharing from Build Pipeline variables
• Solution Ownership from the Power Platform Environment (Query from Service connections)