The `subject` field used in the JWT causes unknown error when using Microsoft AD / OIDC

Microsoft AD/OIDC will not return the `email` claim even if the email scope is requested.

On [Line 339](https://github.com/aws-samples/lambdaedge-openidconnect-samples/blob/b4131275945f8ab0f6f4433b199950575db7c8fc/src/js/auth.js#L339) the cookie is set with a signed JSON Web Token containing a `subject` field that requires `decodedToken.payload.email`, however when that `email` claim is not present the code 500 errors with no details.

Switching to `decodedToken.payload.unique_name` fixes the problem when using Microsoft AD - however whether this is a breaking change for other providers I don't know.

I would like to see a more dynamic why to get the subject for the JWT, or at least extra documentation pointing out this potential issue.

In my code I have replaced any `decodedToken.payload.email` with `getSubject(decodedToken)` and added the following function to the bottom of my `auth.js` file:

```javascript
// getSubject returns a unique identify suitable for the subject field
function getSubject(decodedToken) {
return decodedToken.payload.email || decodedToken.payload.unique_name;
}
```

Commencez dans src/js/auth.js à la ligne 339 et suivez la manière dont decodedToken.payload.email est utilisé lors de la création du subject du JWT signé. Comparez les claims Microsoft AD/OIDC disponibles présentés dans l’issue, puis définissez et vérifiez le comportement pour les fournisseurs avec et sans adresse e-mail ; le travail est terminé lorsque le flux ne renvoie plus un 500 inexpliqué pour la configuration signalée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.