atomic database initialize

[qrkourier]

I observed that the database will partially initialize, leading to an ambiguous initialization state, if the admin password is invalid. This forces day 1 operators to wrap the ziti CLI, detect this condition, delete the database, and try again. It would be better if the initialization operation were atomic.

this is tangentially related to #1973

Repro steps proved time consuming to produce because the ziti pki and ziti create config commands use different default values for file paths, so it will take some time to sort out which env vars need to be aligned. I'll still add repro steps if requested.

I suspect the same problem will manifest if the admin username is invalid.