Sync idpe and quartz org ids in remocal

In prod, quartz and idpe org ids are the same. That is not so in remocal, because quartz-mock provides a mocked org id. This blocks making the app entirely reliant on quartz for organization and user data in dev environments, because many parts of the app need to identify the correct idpe org id in order to perform routing, and to retrieve data relating to the user's org.

Completing this PR requires the following:
1. In remocal (not quartz-remocal), the user's identity (org id and otherwise) should be synced between the mock and idpe, so that it makes no difference whether the user retrieves org and user id from the local idpe instance or quartz-mock.
2. Syncing identities should not change the behavior of e2e tests.
3. Completing this ticket will ensure that navigation (e.g., global header dropdown) behaves identically in remocal to the way that it behaves in prod.