Ban whole_cluster_metadata_notifications test from running with majority read concern off

When running in a sharded multi-statement transaction passthrough on the majority read concern off variant, if two databases used in whole_cluster_metadata_notifications are on different shards, the test will fail. This is due to SERVER-37559, which rejects multi-shard transactions when enableMajorityReadConcern is false.