ID-1109 Fix Admin PATCH User Endpoint

[tlangs]

Ticket: https://broadworkbench.atlassian.net/browse/ID-1109

When using the admin PATCH User endpoint to update the googleSubjectId and azureB2CId for a user at the same time, a database exception occurs. In the query construction, the positions of the new IDs were swapped, meaning the azureB2CId was being saved as a googleSubjectId. Thankfully, the database disallowed the update, as the azureB2CId UUID was too long for the googleSubjectId column.

I've re-worked the logic and added a test to make sure setting both ids works correctly.

---

PR checklist

• I've followed the instructions if I've made any changes to the API, especially if they're breaking changes
• I've filled out the Security Risk Assessment (requires Broad Internal network access) and attached the result to the JIRA ticket

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud