[REFERENCE] feat: incrementally adopt Dashboard BFF API

[adamstankiewicz]

Description

[Context] Tech Spec

• Adds a new queryEnterpriseLearnerDashboardBFF to the queryKeyFactory, integrating with the new Dashboard BFF exposed via [REFERENCE] feat: introduce Gateway Aggregation / Backend-for-Frontend abstraction via LearnerPortalBFFAPIView enterprise-access#572.
• In dashboardLoader, the existing ensureQueryData(queryEnterpriseCourseEnrollments) is now replaced with queryEnterpriseLearnerDashboardBFF, which returns the same enterprise course enrollments metadata in its API response.
• In rootLoader, only executes the ensureQueryData(querySubscriptions) when not a page route configured with a BFF API endpoint. That is, since only the Dashboard page route has a BFF configured, all other page routes continue to work as normal (retrieving data from specific micro-services vs the BFF).
• Updates useEnterpriseCourseEnrollments to compose a new hook useBaseEnterpriseCourseEnrollments. The new hook is responsible for determining which query config to to retrieve enterprise course enrollments. It does so via a resolveBFFQuery helper function that determines which BFF query is configured for any given route pattern. In practice, when on the Dashboard page route, useBaseEnterpriseCourseEnrollments will extract enterpriseCourseEnrollments from the BFF query; when on non-Dashboard page routes, useBaseEnterpriseCourseEnrollments will continue extracting enrollments from queryEnterpriseCourseEnrollments (independent query to enterprise_course_enrollments).
• Updates useSubscriptions with a similar treatment as useBaseEnterpriseCourseEnrollments, described above. useSubscriptions will now extract subscriptions-related data from the BFF query for the current route, if configured; otherwise, falls back to current state querySubscriptions (independent query to learner-licenses).

Jira

ENT-9427

For all changes

• Ensure adequate tests are in place (or reviewed existing tests cover changes)
• Ensure English strings are marked for translation. See documentation for more details.

Only if submitting a visual change

• Ensure to attach screenshots
• Ensure to have UX team confirm screenshots

[adamstankiewicz]

[inform] Abstracted from fetchSubscriptions below. Now re-used along with the BFF response, but these types of transforms should ultimately live in the BFF.

[adamstankiewicz]

The queryClient.ensureQueryData(subscriptionsQuery).then(...) is now conditional based on which route the user is currently on and/or navigating to. If a BFF query is configured for the current page route, the existing fetching of learner-licenses directly is skipped in favor of relying on the BFF query instead (which should fetch the same data and perform the side effects as below).