Change to SSO reader validation

We've made a small change to the validation we run for a reader's login / username to SSO readers.

By default, the Edit Reader page requires that a reader's login / username be a full email address.

However, as one of our customers recently pointed out, some Single sign-on (SSO) setups create logins that aren't full email addresses.

While these reader accounts were properly creating and updating via SSO, any manual changes made to the reader in the Edit Reader screen weren't being saved because the login/username was failing our built-in email address check. This basically made it impossible to manually edit SSO readers in any way. While SSO generally handles the account administration, there are a few workflows that still require manually editing SSO readers, such as using KO-only reader groups in addition to or instead of SSO-provided reader groups.

We've updated the logic on this page so that if a reader is designated as logging in through SSO, we allow non-email address login/username. The email address format is still required and enforced for all other reader accounts.