Don't call IEnumerable<IUserEventHandler> from UserDisplayDriver

[hishamco]

Fixes #17072

[MikeAlhayek]

I don't think this is a valid approach and should be tested.

Currently users are able to enable or disable users via the handler. So you can implement the handler, the enable or disable the user. With the proposed approach these events are fired after the user is updated which ignores the handlers logic.

What I think should happen here is that we should move the function to enable/disable user outside the Form edit request similar to the approach I did for confirming email in PR #17684

Moving the disable/enable process as part of the Actions button will allow us to properly call the handlers outside the process of updating the data form.

[hishamco]

With the proposed approach these events are fired after the user is updated which ignores the handlers logic.

What's the wrong with that while enabling / disabling the user should trigger updating event

[MikeAlhayek]

The ToggleStatus action in the controller will update the User object and call the UserStore.Update "which will trigger the updating and Updated events. This will also normalize the process

[hishamco]

The current approach will open the possibility to listen to the event outside the OC without accessing the control

[MikeAlhayek]

Yes but the proposed will not work. Did you test it out or you assumed the code is good?

[hishamco]

It works fine after disabling UserDisabledEventHandler which makes the app enter an infinite loop. I'm not sure why you are regenerating the user stamp here.