Add verified config to scenario documentation

[cloudmadlab]

I have been noticing that certain commands in some scenarios are experiencing different results depending on the source/target operating system selection. For example, I have been attempting the AzSHCI and Kubernetes and AzSHCI Deployment scenarios and experienced different results with the following two OS combinations:

• WS 2019 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.
• WS 2022 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.

I haven't had an opportunity to go command-by-command and organize my varying results yet. However, it might be helpful to specify the exact environment that has been verified in the scenario documentation. For example, note in the documentation that you experienced no issues with the code running on a WS 2022 DC against 21H2 nodes.

[jaromirk]

Hmm, the idea is to have LabConfig for each scenario (except DC, there are all VMs defined with OS I was testing last). Assuming everyone will use the same. I did not face any issue so far with different update level of certain server. What I recently faced with for example Kubernetes scenario are different issues with az. modules. I tried to document all issues as reference to GitHub issue I created for each az. module