[12929] Properly adding idme_uuid as a field when user model is reloaded

[bosawt]

Summary

• This PR makes it so that user.idme_uuid properly persists after the User model is reloaded (when the User redis expires and is recreated), specifically for users authenticating with DSLogon and MyHealtheVet.

Related issue(s)

• Fix issue with Sign in Service user reloader, where idme_uuid did not persist for DSLogon and MHV accounts after the User model was expired and reloaded #12929

Testing done

• Authenticated with DSLogon on Sign in Service
• On Rails console, deleted the User model associated with the redis that was created for the authenticated user
• Called an authenticated route, and confirm that the User model was recreated, and that user.idme_uuid is not nil

What areas of the site does it impact?

General Application usage for DSLogon and MHV clients (who are authenticated with Sign in Service

Acceptance criteria

• Authenticate with DSLogon or MHV with Sign in Service
• On Rails console, find the user redis model User.find(<idme_uuid>) where idme_uuid is the backing idme_uuid for the account
• Delete the redis model
• Call any authenticated route, and confirm the redis model was recreated (User.find(<idme_uuid>) does not return nil)
• Confirm that user.idme_uuid is not nil

[rileyanderson]

Looks good to me. My User was recreated after destroying it 🚀