mongo: should raise validation error when configurable parameters are passed in to URI

[jgao54]

Currently, passing a single node with /?directConnection=true shouldn't work because they don't support replication but it goes through and gets stuck in provisioning.

To have a predictable and consistent behavior, we should restrict configurable parameter values from being passed in via URI (currently we only flag if username/password are passed in).

[heavycrystal]

had to revert because Altas issue

[jgao54]

Fixed by #3349

Tested validation now catches the case when it receives a direct connection to a standalone node, and return an errors message:

failed server compatibility validation: topology type must be ReplicaSet or ShardedCluster

Tested both cases where (1) directConnection=True is passed in (2) it's not explicitly passed in to the uri but node is not a replicaset or sharded cluster (the real issue has to do with running mongo in standalone mode does not support changestream api).