Issue title: Specify email address in LoginWith 
 Issue body: Hi,

when login with an OpenID provider for the first time, I would like to set email without triggering email verification.
Indeed, `email` is already verified by upstream OpenID provider. 

We could modify the `loginWith` method :
```
ParseUser.loginWith(String provider, AuthData authData, {String email});
```

That way, `email` is set during the `POST /parse/users`, and email verification is not triggered.

Any thoughts about that ?
 Comments: 
 Comment 0: # In Parse Server REST GUIDE
there are two methods to register user with third party provider:

## POST /parse/user
Sending only authData in body request, this will create a new user with random username, random password. Other user's properties are ignored.

## POST /parse/user
Sendind json body containing user's properties AND authData property, this will create a new user linked to third party provider, setting all properties set in json body into user's record.

### Example:

**Register only with AutData:**

**Request**
```
curl --request POST \
  --url https://{parseServerUrl}/parse/users \
  --header 'Content-Type: application/json' \
  --header 'X-Parse-Application-Id: {appId}' \
  --data '{"authData":{"provider":{"access_token":"accessToken","id":"id","id_token":"id_token"}}}'
```
**Result**
created user as json:
```json
{
"objectId":"objectId",
"username":"generated",
"password":"*********",
"email": "undefined",
"authData":{"authData":{"provider":{"access_token":"accessToken","id":"id","id_token":"id_token"}}},
"emailVerified": "undefined",
"updatedAt": "....",
"createdAt": ".....",
"ACL": "...."
}
```

**Register AutData and User properties:**

**Request**
```curl
curl --request POST \
  --url https://{parseServerUrl}/parse/users \
  --header 'Content-Type: application/json' \
  --header 'X-Parse-Application-Id: {appId}' \
  --data '{
"username":"username",
"password":"password",
	"email": "abigail50@example.org",
	"authData":{"google": {"access_token":"accessToken", "id":"id", "id_token": "idToken"}}
}'
```
**Result**
created user as json:
```json
{
"objectId":"objectId",
"username":"username",
"password":"*********",
"email": "abigail50@example.org",
"authData":{"google": {"access_token":"accessToken", "id":"id", "id_token": "idToken"}},
"emailVerified": "undefined",
"updatedAt": "....",
"createdAt": ".....",
"ACL": "...."
}
```

# In Parse SDK 

In dart/flutter SDK, only **Register with AutData** is possible.
It can be a problem. In our app, we need to set user's email from google or facebook.
To do that, we update the user setting email BUT this trigger emailVerification (and we don't want verification for user from third party providers) .

To respect REST guide, i think we must do something like this:

ParseUser38d1:d2b4:3d06:83e8:96a5:8c2:893d:aba5loginWith
Should take an optional params {String email, String username, String password};
Then create a new user with ParseUser.createUser(username, password, email);

ParseUser38d1:d2b4:3d06:83e8:96a5:8c2:893d:aba5_loginWith
Should send in body request toJson() and authData, not only authData.

I'm testing it on our fork, we will do a PR when it's ok for us.
 Comment 1: We are closing issues that have been open for a long time without activity. 
This will make it easier to organize things from now on.
If the problem persists, please open a new issue.
Thanks.
 Comment 2: loginWith('facebook', authData) also gives me an error: `Facebook auth is invalid for this user`. What should I do? I am using the latest version of parse_server_flutter
 Comment 3: The problem is not in the package. 

Android or iOS project?

 it is some wrong or not done configuration in the Back4app or in your project.

check all configurations. 
 Comment 4: 
The problem is not in the package.

Android or iOS project?

it is some wrong or not done configuration in the Back4app or in your project.

check all configurations.
 Comment 5: Yes. I think the problem is in back4app loginWith. As far as i know, all
configuration are correct. Their support team is unresponsive at the moment

On Sat, Aug 14, 2021, 11:59 PM Rodrigo de Souza Marques <
***@***.***> wrote:

> The problem is not in the package.
>
> Android or iOS project?
>
> it is some wrong or not done configuration in the Back4app or in your
> project.
>
> check all configurations.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/parse-community/Parse-SDK-Flutter/issues/506#issuecomment-898911723>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AK27WTV5ZN4DJUOBM4OVJALT42HHHANCNFSM4TUS5OZQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
> .
>

 Comment 6: I have two projects set up with Facebook in Back4app working (including the one in the guide)

Delete Facebook App Id and add again.

Retest.
{'source': 'GithubIssues', 'repo_name_with_owner': 'parse-community/Parse-SDK-Flutter', 'issue_id': 742456851, 'repo_stars': 367.0}