Design entra-powershell with ALC bridge pattern for a more robust assembly load handling

Describe the feature
People usually use not only one but several PowerShell modules, which often cause assembly conflicts depending on the order the modules were loaded or used.

Developers of a given module often "lives in a bubble" where everything inside the module works fine, but in real-life scenarios, where multiple modules from multiple providers are used, they might fall short due to assembly load design of the module.

Enter Assembly Load Contexts (ALCs). ALCs were introduced in .NET Core 1.0 to specifically address the need to load multiple versions of the same assembly into the same runtime.

ALC is the "new" way of loading assemblies in PowerShell 7, and should have better ways of handling multiple versions of the same assembly. There are a few samples in the code below that show how to avoid this breaking code into two modules and using the IModuleAssemblyInitializer to lazy load and undload assemblies into ALC.

https://learn.microsoft.com/en-us/powershell/scripting/dev-cross-plat/resolving-dependency-conflicts?view=powershell-7.3#more-robust-solutions

How will this feature enhance your project and further the project’s overall goals? Who will benefit from this feature (i.e. all users; the project team)?
Try and do a search on Az, MgGraph, PnP.PowerShell github issues lists or other foras. One of the most common issues with PowerShell modules are assembly conflicts (our new "dll-hell") due to the fact that a module loads a dll when a certain function is used, and depending on module versions and order the involved PowerShell modules was loaded, errors will occur.
ALC bridging pattern makes it possible to load multiple versions of the same assembly, hence minimizing the assembly conflicts and resulting in a more robust module and less frustrated users :)

Describe alternatives you've considered

Additional context

Start with the linked PowerShell dependency-conflict guidance and its Assembly Load Context bridge samples, then inspect how this module currently loads assemblies. The issue names no files or tests; completion would require agreeing on the bridge design and demonstrating that multiple module versions can load without assembly conflicts.