(feat) O3-5754: Update login location picker to use user-scoped endpoint

[solomonfortune]

Requirements

• This PR has a title that briefly describes the work done including the ticket number.
• My work is based on designs, which are linked or shown either in the Jira ticket or the description below.
• My work includes tests or is validated by existing tests.
• I have updated the esm-framework and storybook mocks to reflect any API changes.

Summary

Replaces the generic GET /ws/fhir2/R4/Location call in the login location picker with a user-scoped endpoint GET /ws/rest/v1/user/{uuid}/location, so users only see locations relevant to them. The user UUID is sourced from useSession().
Fallback logic lives entirely server-side, so deployments without user-location mappings are unaffected.

Screenshots

No UI changes.

Related Issue

https://openmrs.atlassian.net/browse/O3-5754
https://openmrs.atlassian.net/browse/TRUNK-6669

Other

⚠️ Draft — blocked on TRUNK-6669.
Backend endpoint not yet implemented. Ticket still at needs assessment stage

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7cb9f71

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
14.9% Duplication on New Code

See analysis details on SonarQube Cloud