Problem: The organization creation flow does require the user to enter an organization email address. As established in PROJQUAY-6975 this is actually optional data and should contain an auto-generated UUID-like string. This is also the behavior of the old UI.

Expected behavior: The organization creation flow should optionally support entering an organization email address and only require it, when the UI support Quay.io. This should be implemented in line with the behavior of the old UI. When email address is not given, the organization's email data field should store a UUID value.

Actual behavior: The organization creation flow forces the user to enter an email address and also validates the pattern, therefore creating the impression, that the system needs a functioning, unique email address for organizations to work.