Resolves Issue #1735 and #1736, Preventing UUID changes on update requests

[afoote-mitre]

Closes Issue #1735 and #1736

Summary

UUID changes were technically allowed by the update user and org function calls. These changes allow for UUIDs to still be passed into the request if they match the existing values, while preventing attempts to update existing UUID values.

Important Changes

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

• Added verification to allow for matching incoming UUIDs on update requests, while ignoring attempts to change UUIDs on update requests
  src/controller/registry-org.controller/registry-org.controller.js
• Added verification to allow for matching incoming UUIDs on update requests, while ignoring attempts to change UUIDs on update requests

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