Developer Portal "Analytics" widgets show "No data" and report page errors, while data is available in Azure Portal

## Bug description

The **Analytics** widgets and reports in the **Managed Developer Portal** show **“No data”** messages even though analytics data is available and visible in the **Azure Portal → API Management → Analytics** section.

The affected analytics widgets include metrics such as *Total Calls*, *Successful Calls*, *Failed Calls*, *Bandwidth*, and *Top APIs*. All of them display “No data” to the developer user.

Confirmed that both the **user** and **subscription** are the same ones being used in the Azure Portal — data is available there but not rendered in the Developer Portal.

When navigating to the **Reports** page through the portal builder, multiple error notifications appear on the right side:
> “Oops, something went wrong. We are unable to complete your operation this time. Please try again later.”

This strongly suggests the issue is specific to the portal backend or its data query layer, not to APIM itself.

The admin analytics:

The developer analytics:

And the analytics page using admin mode:

## Reproduction steps

1. Log in to the **Managed Developer Portal** with a developer account that has active subscriptions and API activity.
2. Navigate to the **Analytics** or **Reports** page.
3. Observe that widgets show “No data” or fail to load metrics.
4. Optionally, edit the page in **Portal Builder** mode — observe multiple “Oops, something went wrong” errors appearing on the right.
5. Compare with the same metrics in **Azure Portal → API Management → Analytics**, where data is correctly populated.

## Actual behavior

- Analytics widgets in the Developer Portal display “No data”.
- The report page triggers multiple “Oops, something went wrong…” errors.
- Console logs show failed API requests or JavaScript errors related to data fetch.
- Analytics data is verified to exist in Azure Portal under the same subscription and user.

## Expected behavior

- Analytics widgets and reports should correctly display usage data available in APIM (calls, bandwidth, errors, etc.) when accessed by the same developer with the same subscription.
- The Reports page should load without any “Oops, something went wrong” errors.

## Is self-hosted portal?

No (Managed Developer Portal).

Start by reproducing the failure in the Managed Developer Portal Analytics and Reports pages, comparing failed requests and console errors with the working Azure Portal data. Check the Portal Builder Reports flow as well; done means developer widgets show calls, bandwidth, errors, and Top APIs, while the Reports page loads without error notifications.

Written by the indexing model from the issue text.