🐛 Bug Report: OAuth2 implementation does not enforce email retrieval

### 👟 Reproduction steps

Currently, when the user is presented with the Facebook oauth screen, the user can select 'Edit access" and then switch off the email.
This means that, after the user disables the email and clicks Continue, a new user will be created in Appwrite but without an email address.

Similar thing is happening with the Yandex OAuth2 adapter - users are created but without email address.

Discord post - https://discord.com/channels/564160730845151244/564175717521424424/1007611652750970900

### 👍 Expected behavior

Appwrite should extend the OAuth2 adapters to always enforce the retrieval of email address

### 👎 Actual Behavior

Users are created without an email address

### 🎲 Appwrite version

Version 0.15.x

### 💻 Operating system

Windows

### 🧱 Your Environment

_No response_

### 👀 Have you spent some time to check if this issue has been raised before?

- [X] I checked and didn't find similar issue

### 🏢 Have you read the Code of Conduct?

- [X] I have read the [Code of Conduct](https://github.com/appwrite/appwrite/blob/HEAD/CODE_OF_CONDUCT.md)

Inizia individuando le implementazioni degli adapter OAuth2 di Facebook e Yandex e il percorso di creazione degli utenti. Traccia come viene richiesto e gestito l’accesso all’e-mail; il lavoro è completato quando entrambi i provider non possono creare utenti senza un’e-mail e c’è una copertura di regressione per i casi di e-mail disabilitata o mancante.

Scritto dal modello di indicizzazione a partire dal testo della issue.