Ensure failures at details modifications are recoverable

[Supereg]

Problem

Several async calls have to complete such that an account detail modification is considered successful.

1. Updating the email address.
2. Updating the password.
3. Updating the display name.
4. Update externally stored account details.

The update might fail at any step and results that a modification is only partially applied. At the same time, we account details are never refreshed. Partial updates are persisted in the service-side, but never display on the client-side.

Solution

There is generally no good approach to revert updates that have already been applied. Therefore, the best solution is probably just to ensure that updated details are properly displayed to the user.

Additional context

This is not a problem in practice, as these combinations never happen in practice. The Account Overview UI either updates the email, password and display name individually or all externally stored details at the same time.

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines

[PSchmiedmayer]

@Supereg Thank you for documenting this! I agree; we shouldn't bother to try to revert any changes. I would also suggest to transparently display any updated values and keep any non-updated values as they are so the user has a up-to-date overview of the account details. An error alert saying that certain fields could not be updated could be part of the UI flows.