Support different contexts per runspace/thread

We have a service which manages cost and security governance across several thousand tenants. This service runs in Azure Functions, which scales out by creating additional Powershell runspaces. The challenge is that the msgraph cmdlets only have a single per-process context which changes when calling Connect-MgGraph.

This causes the following behavior:

1. Runspace 1 calls Connect-MgGraph -TenantId <Tenant 1> and starts running other graph commands.
2. Runspace 2 starts and calls onnect-MgGraph -TenantId <Tenant 2>.
3. Runspace 1 incorrectly executes its commands against Tenant 2.

Our service also manages Azure subscriptions using the Az cmdlets. Az cmdlets solves the multiple runspace issue by providing the -DefaultProfile parameter on all commands. This allows each runspace to execute independently against different tenants and subscriptions. The pattern looks like:

$ctx = Connect-AzAccount -Tenant $TenantId -Subscription $SubId
Get-AzVM -DefaultProfile $ctx

Ask:
Provide a common -DefaultProfile type of parameter for all msgraph cmdlets which allows for a saved context to be utilized.

Start by tracing Connect-MgGraph and how the Microsoft Graph cmdlets store and retrieve their process-wide context; the issue does not name specific files or tests. Define how a shared DefaultProfile-type context would be created and passed so separate runspaces can target different tenants independently, then verify the pattern across the cmdlets.