When launching clusters using mongo-orchestration, auth.json and auth-ssl.json removed arbiterOnly:true back in 2018 to work around SERVER-34421. After SERVER-34421 was resolved, these configuration changes were never reverted. This resulted in auth-enabled replica sets in our test environments running with 3 data-bearing nodes and no arbiter.

Unfortunately 27017 and 27018 ran with a 500MB oplog, but 27019 ran with a 100MB oplog. This led to sporadic node failures if 27018 ended up tailing 27019 - which could result in 27018 falling off the oplog and fasserting as happened in the .NET/C# driver during times of heavy oplog churn.

This ticket is to revert this commit from drivers]evergreen-tools so that all replica set test configurations run with two data-bearing nodes (27017 and 27018) and one arbiter (27019).