Epic - Eliminate Cloud2 Reliance on IDPE API Calls For Data Provided By Quartz

Newly created quartz endpoints like `/quartz/identity` obviate the need to make any calls to retrieve the user's name/id and organization name/id from IDPE. These IDPE calls should be removed from the cloud portion of the UI. Instead, the data should be pulled from quartz selectors based on the data now being provided by quartz.

The business rationale for doing this is to avoid the burden of unnecessary API calls to our backend, and allow us to potentially retire IDPE endpoints that no longer have independent value.

Implementing this epic requires a rework of quartz-mock and its relationship with remocal. Because the organization ID is part of the path for accessing most of the app, relying on the quartz-generated org id at the highest levels of the app would attempt to generate paths using the mocked quartz org ID, rather than the org ID automatically generated by IDPE.

In prod, those org ids are the same, but because of the presence of the mock, they are _not_ identical in remocal, and implementing this change would cause the app to fail to load in dev environments. Remocal environments will need to be changed so that mocked org ids in quartz are synced with IDPE org ids so that, like in prod, they are guaranteed to have the same value.

## Business Goal

Reduce unnecessary load from calls to IDPE APIs. May permit removal of these endpoints (to be discussed with services team).

## Target Audience

Internal. Removal of unnecessary API calls benefits UI and AIM teams.

## Core Team
- Engineering Lead: @wdoconnell
- Product Lead: @ALuckette

## Extended Team

@StacieClark @randycoulman @influxdata/dumplings