allow a custom API scope to be specified on Web or OData data source

Per Connecting with Microsoft Entra ID using the Web and OData connectors (https://learn.microsoft.com/en-us/power-query/connector-authentication#connecting-with-microsoft-entra-id-using-the-web-and-odata-connectors), if a Web or OData data source is "https://api-gateway.domain.com/api", Power Query assumes a target Application URI of "https://api-gateway.domain.com/.default" when fetching access tokens from Entra ID. The problem is: we have APIs from many disparate teams / organizations behind our enterprise Azure API Management Gateway, and each API owner manages access to their API using their own Entra ID app registration. This approach would be considered best practice by Entra ID / OpenID Connect / OAuth 2, but isn't supported by Power Query. Please enhance the Power Query Web/OData configuration, as well as the Power BI Data Gateway "Service Principal" authentication method, to allow specifying a custom API scope (e.g., Scope: api://my_team_api.domains.com/.default) for the data source. This will allow API owners to continue using their own Entra ID app registration to manage API access, rather than forcing disparate APIs to be managed by a single Entra ID app registration just to support Power Query / Power BI Data Gateway.