[Issue] ADX/Kusto connector wizard missing "Use managed identity as federated identity credential" checkbox — blocks cross-tenant Kusto access

Title:

Body:

Summary The docs state MI + FIC is the only supported method for cross-tenant Kusto access, but the Azure Data Explorer connector wizard exposes no way to configure it. The capability appears to exist in the runtime but has no configuration surface.

Expected Per capabilities/cross-tenant-access.mdx → "What you can do cross-tenant": Query Kusto databases | Azure Data Explorer | MI + FIC | Kusto connector. The same page's "How MI + FIC works" section explicitly covers Kusto: "For Kusto connectors, the platform's outbound proxy handles token injection automatically... using the FIC-configured identity."

Actual The ADX connector wizard (Builder → Connectors → Add connector → Azure Data Explorer) has no FIC checkbox at any step — Set up connector, Add clusters, or Review + test. Only Name, Managed identity, and per-group Managed identity are available. The checkbox is present only in the Azure DevOps "Add repository" wizard.

Evidence the runtime supports it The agent's own connector configuration models all three properties on Kusto and KustoClient connector types:

useManagedIdentityAsFic
federatedClientId
federatedTenantId

Start with the Azure Data Explorer connector wizard steps named in the issue and compare them with the Azure DevOps Add repository wizard, where the checkbox already exists. Read capabilities/cross-tenant-access.mdx and inspect the Kusto and KustoClient configuration models for useManagedIdentityAsFic, federatedClientId, and federatedTenantId. Done means the ADX wizard exposes and preserves the FIC settings for connector configuration.

Written by the indexing model from the issue text.