Add missing user fields provided by Twitter

[mlafeldt]

See https://developer.twitter.com/en/docs/twitter-api/v1/data-dictionary/object-model/user

Here's the raw JSON for my Twitter account copied from the Auth0 console:

{
    "created_at": "2021-02-09T17:32:08.973Z",
    "description": "Freelance cloud consultant by day. Aspiring product builder by night.",
    "identities": [
        {
            "provider": "twitter",
            "user_id": "295919262",
            "connection": "twitter",
            "isSocial": true
        }
    ],
    "location": "Hamburg 🇩🇪",
    "name": "Mathias Lafeldt",
    "nickname": "Mathias Lafeldt",
    "picture": "https://pbs.twimg.com/profile_images/1069419719227146240/e8l9msvL_normal.jpg",
    "screen_name": "mlafeldt",
    "updated_at": "2021-02-11T08:56:51.590Z",
    "url": "https://t.co/jXqmcnVmL5",
    "user_id": "twitter|295919262",
    "blocked": false,
    "last_ip": "1.2.3.4",
    "last_login": "2021-02-10T22:10:18.916Z",
    "logins_count": 3,
    "blocked_for": [],
    "guardian_authenticators": []
}

[mlafeldt]

Those whitespace changes were done by gofumpt. I can revert them if you want.

[mlafeldt]

@alexkappa Could you please merge this and #196? A new tag would also be appreciated. 😊

[mlafeldt]

🙏

[jbauth0]

LGTM ... I'm pretty sure there are only restrictions on reserved root level fields. I don't know if there is a definitive list of these fields but for example a custom saml assertion attribute will just get added at the root level unless a Rule maps it elsewhere.