Problem Statement,
_**What is the problem?**_ MongoDB Agent (Automation Module) attempts to auth with `net.tls.clusterFile` / `net.tls.certificateKeyFile` X.509 certificate first, pretending it is a Replica Set member.
_**Why is this a problem?**_ MongoDB Server process logs are flooded by unnecessary noise from such MongoDB Agent (Automation Module) auth attempts pretending it is Replica Set member. MongoDB Server will always log Replica Set member auth certificate usage outside of internal MongoDB Server client (https://github.com/mongodb/mongo/blob/6212e50e73dd032b448a514fe6893c6490a28a9f/src/mongo/db/commands/authentication_commands.cpp#L294-L300),
Example,
{"t":{"$date":"2021-05-10T11:08:03.110+0000"},"s":"W", "c":"ACCESS", "id":20430, "ctx":"conn116","msg":"Client isn't a mongod or mongos, but is connecting with a certificate with cluster membership"}
Proposal,
* Don't attempt to auth with X.509 certificate from `net.tls.clusterFile` / `net.tls.certificateKeyFile` MongoDB Server parameters and use MongoDB Agent X.509 certificate configured.
