When a new user invitation is created and the username already exists in key cloak, then an error should be generated right away and that new user invitation should not be.
However, if such an invitation ends up being created in the step of the invite acceptance process where the user creates a password at that moment, it reaches out to Key Club to create the user and key clerk will give an error saying the user doesn't exist. This results in a sad tuba error. That should be handled too