[Epic] Support cross-tenant identity from .NET worker extensions

[mattchenderson]

Description

To support cross-tenant triggers, we need to leverage federated identity credentials. The Azure SDK team has updated Microsoft.Extensions.Azure to enable this (changelog from release prep). We therefore need to update to version 1.12.0. This brings a few transitive dependency bumps, the most notable of which is moving to version 8.0.0 of Microsoft.Bcl.AsyncInterfaces. See the host PR for the same changes.

The host PR itself is insufficient, as the trigger load context will ultimately derive the version from the host extension version specified by the worker extension. New versions of host extensions which reference 1.12.0 are coming, but they might not all be released at once. In addition, any of our extensions leveraging deferred bindings on the worker side must also be able to properly handle the same configuration. Each worker extension seems to reference their own version of Microsoft.Extensions.Azure, and there is variance among them.

There are therefore two aspects to this work item:

• Update the host extension version specified by the worker extensions
• Update the worker extension dependencies on Microsoft.Extensions.Azure (in cases where deferred binding is used)

Documentation will need to be updated, and it will need to be qualified per extension. We therefore need the same granularity of tracking this work. Child items will be created for each impacted extension. Both of the above aspects should be tackled at once if possible.

As part of this work item, we might consider Central Package Management to help provide a unified base. We can simultaneously update the extensions not using deferred bindings.