As a CI best practice, we shouldn't run multiple test suites from inside the same bash script in evergreen.

• This is opaque when viewed from evergreen, because not all tests show up in the evergreen CI as tests.  This leads to confusing behavior where a task fails but all tests for the task succeed
• This leads to a lack of discoverability about what we actually test (as an example, I discovered by accident that our socks5 tests actually also run the full csfle test suite twice only when they started failing).

If we decide that testing socks5 proxy support with csfle is something we officially support (most likely yes), these should be broken into separate evergreen tasks for visibility and maintainability.

Acceptance Criteria

• Create separate evergreen tasks for:
  • socks5 with auth
  • socks5 without auth
  • csfle + socks5 with auth
  • csfle + sock5 without auth
• Refactor the socks5 and csfle test CI scripts as needed

Open Questions

We currently test csfle both against master and a pinned commit in libmongocrypt.  Should we also do this for socks 5?  If not, should we be testing against master or a pinned commit?  We should make this explicit by explicitly pinning whichever we choose.