Multi database replication requires global `replicate_to_remote`

A single database uses its local dolt config to replicate to a remotes on dolt commit ([relevent docs](https://docs.dolthub.com/sql-reference/server/replication#configuring-a-primary)). A database defines a valid remote with a name `dolt remote add `, and then the named remote is indicated for pushing commits: `dolt sql -q "set @@persist.dolt_replicate_to_remote = ''"`

A multi-database server requires the first step for all individual databases - a valid remote with a common name. But the `dolt_replicate_to_remote` session variable appears to be initialized from the global config. The local values for `replicate_to_remote` are ignored.

The additional step for a multi-database server is `dolt config --global --set sqlserver.global.dolt_replicate_to_remote `.

This is confusing for users. It is probably not ideal to force replication for all of a computer's databases through a global variable. This is related to a broader set of problems regarding how Dolt's CLI-designed configuration has not translated cleanly to a multi-database server UX.