Registration - Directly populate both Drupal and Dataverse on Registration

[adam3smith]

Currently, actually having the accounts show up in Dataverse and Drupal involves three steps:

1. Create account
2. Log in and accept GTCU (Drupal account is created)
3. While logged in, navigate to Dataverse (Dataverse account is created)

In most cases, this just works because it's a natural flow, but we are seeing a fair amount of issue, most commonly when asking a co-author to create an account to add them to an existing dataset.

Desired behavior:
On account creation, all three databaseses are immediately populated (LDAP, DV, Drupal). Any action should still require accepting GTCUs.

[qqmyers]

FWIW: This has been improved with our current Keycloak/OIDC-based SSO. If a person completes the reg form (to create an account or to finish a first-time social login), the Dataverse and Drupal accounts are all created automatically. The one remaining inconvenience I've noticed is that if someone does a social login and doesn't complete the reg form, an incomplete Drupal/LDAP entry is created. If a user in this situation comes back, they are again directed to the reg form and things would continue as normal from there.