Problem configuring a new database with the multiversion client

I've seen problem configuring new databases through the client library rather than the CLI. It seems like it will only be able to configure a new database if the server's version does not match the primary client version. I have been able to change database configuration with the multiversion client, so it seems to be specific to initialize a new database.

Start by reproducing new-database initialization through the client library and the CLI with matching and differing server and primary client versions. Compare the initialization paths with the existing multiversion configuration behavior; done means a new database can be configured successfully through the client library when versions match.

Written by the indexing model from the issue text.