Resolves #1730, Fix database inconsistency with account cleanup

[afoote-mitre]

Closes Issue #1730

Summary

If the user exists in at least one of the schemas, the administrator must be allowed to modify, deactivate, or rotate secrets on whatever records do exist, rather than throwing an unhandled exception

Important Changes

src/repositories/baseUserRepository.js

• Updated updateUser(), updateUserFull(), and resetSecret() to handle cases where a user exists in at least one but not necessarily both schemas.

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
• 3) Ensure test case outlined in original ticket succeeds as expected