Currently, when saving a connection in the new connection form we transfer the connectionInfo into the old connection-model and then save it.
At some point in the conversion and saving the connection-model validates the model. This causes some unforeseen errors as we're more flexible and permissive with connections in the new connectionInfo. When these errors occur the model is not saved. This ticket involves removing that validation with connections that are saved using the new connection form. We should ensure that this doesn't not break the existing

An example for testing this is using a connection string with the `authMechanism` not fully capitalized:
"authMechanism=SCRAM-sha-1"
mongodb://a123:b123@localhost:27017/?authMechanism=SCRAM-sha-1
Saving this connection string as a favorite is a shortcut to show this behavior.