Resolves issue #1673, Handling read-after-writes in the registry user controller

[afoote-mitre]

Closes Issue #1673

Summary

Properly handling read-after-writes in the registryUserController, through the use of casualConsistency and some minor reordering of calls

Important Changes

src/controller/registry-user.controller/registry-user.controller.js

• Added casualConsistency: false to updateUser(), grantRole(), and revokeRole()
• Moved the generation of updatedUserUUID before the mutation execution blocks, matching the process for requestingUserUUID

Testing

Steps to manually test updated functionality, if possible

• 1) Run npm run test:integration and ensure all tests pass
• 2) Run npm run test:unit-tests and ensure all tests pass