Provision a Provider via JVM: provider data is not being added to authenticationproviderrow

What steps does it take to reproduce the issue?
The issue was encountered in the SPA OIDC integration code: https://github.com/IQSS/dataverse-frontend/issues/565
The easiest way to recreate the issue is to setup the SPA development environment described in issue 565

After running ./run-env.sh 10959-bearer-token-auth-ext, check the Postgres table authenticationproviderrow. It should contain a row for the OIDC provider, but it only has one row, for the builtin user.

• When does this issue occur?
  Configuring a dataverse for OIDC provider using JVM options

• Which page(s) does it occurs on?
  The missing data preventing the user from being shown in Admin Dashboard -> Manage Users

• What happens?

• To whom does it occur (all users, curators, superusers)?

• What did you expect to happen?
  a row in the table should exist for the OIDC provider

Which version of Dataverse are you using?
The 10959-bearer-token-auth-ext image

Any related open or closed issues to this bug report?
https://github.com/IQSS/dataverse-frontend/issues/565

Screenshots:

The authenticateduser table, showing an OIDC user successfully registered in the Dataverse:

The oidc user was also added to authenticateduserlookup:

The oidc provider is missing from authenticationproviderrow:

Start with the setup described in issue 565 and run ./run-env.sh 10959-bearer-token-auth-ext. Compare the OIDC provider data in authenticationproviderrow with authenticateduser and authenticateduserlookup, then trace JVM-option provisioning; done means the OIDC provider has a row in authenticationproviderrow and remains available in Admin Dashboard → Manage Users.