Implement proper assembly isolation to play nice with `vscode-powershell`

### Description

According to `vscode-powershell` maintainers, Azure PowerShell does not "implement assembly isolation correctly across the board".

*

This can cause assembly conflict issues that `vscode-powershell` can't solve easily from their context.

I don't have deep knowledge about this, I just want my authoring experience where Microsoft owns every part of the stack fixed.

Here are some resources on how, using assembly load context (ALC):

*
*
*
*
*

Here is more context:

* 2020-10-15:
* 2023-09-05:
* 2024-09-30:

### Feature request

Use AssemblyLoadContext for **all** assembly dependencies used by **any** Az module.

Start by reviewing the linked vscode-powershell reports, AssemblyLoadContext resources, and the PowerShell-ALC-Samples project to understand the dependency-loading problem. Then locate how Azure PowerShell modules load assembly dependencies; done means all assembly dependencies used by Az modules are isolated with AssemblyLoadContext and no longer conflict with vscode-powershell.

Written by the indexing model from the issue text.