SERVER-139492In Code Review
Split evergreen tasks for C++ integration tests
Currently, the C++ integration test tasks are organized according to the fixture they spawn or what feature flags and server paramters they use. For an example of simple fixture-based organization, integration_tests_replset is most C++ integration tests that run against a replica set. For an example of feature flagging, {{integration_tests_standalone_grpc}} runs a small set of C++ integration tests against a server with ingress gRPC enabled. To support infinite burndown, this change splits thos