Fix sign-in loop when email is not set in Azure AD account

[heguro]

Fix #273, May related: #408, #418

The profile object returned when signing in from Azure AD may be missing the email property.
In this case, the following will occur.

1. The following code will fail on profile.email.toLowerCase(), so AzureADProvider doesn't return profile and cause an sign-in loop.

   • azurechat/src/features/auth-page/auth-api.ts

     Line 47 in f53e525

     adminEmails?.includes(profile.email.toLowerCase()) ||

2. The email property is used in the userHashedId function to identify users in the database, but if the email property is undefined, the hashing fails.

   • azurechat/src/features/auth-page/helpers.ts

     Lines 28 to 32 in f53e525

     	export const userHashedId = async (): Promise<string> => {
     	const user = await userSession();
     	if (user) {
     	return hashValue(user.email);
     	}

In this PR, if the email property is missing, the preferred_username property, which contains the user principal name, is used as the email instead.

(Note: Personally, I believe using an immutable identifier like sub for userHashedId would be more robust than using email or preferred_username (which Microsoft's documentation states are mutable). However, implementing this idea is not included in this PR to maintain compatibility with previously stored data.)

[yasir-fayrooz]

+1 on this. Was about to make the same PR

[bwitzig-zen]

+1 for this request.

Some orgs don't have the email field setup in O365 and this will allow them to not require an additional step for onboarding the app

[oliverlabs]

@thivy - this needs to be merged to main.

[oliverlabs]

Approved.