ci(NODE-6505): Setup CI

[aditi-khare-mongoDB]

Descriptions
This testing framework is being added in to allow for ease of encryption testing in PRs to come.

Add CI configuration to ensure that FLE can be end-to-end tested in the mongoose repo.
Add scripting so users can test locally and understand how the CI configuration works.

Summary of Changes

• Add scripting to setup CI for mongoose integration tests locally and through GHA
• Add script to setup encryption cluster locally for local user testing
• Add basic integration testing to check the CI has been setup correctly

[baileympearson]

This is a great start!

Along with the comments, we also need the ability to set up a cluster and run tests locally. Can we add a script that uses drivers-evergreen-tools to set up a cluster for local development as well as using the github action?

[baileympearson]

Intentionally commented out?

[aditi-khare-mongoDB]

Just so any push triggers the action, I've added this branch name into the push config for clarity - will remove it when we're ready to merge.

[baileympearson]

Do we want to be able to trigger the action manually, or is on "push" / "pr to master" sufficient?

[aditi-khare-mongoDB]

I think manually would be nice especially as we continue encryption testing development and if Val or another mongoose contributor adds any encryption functionality.

[baileympearson]

I think this was missed from my initial review:

Along with the comments, we also need the ability to set up a cluster and run tests locally. Can we add a script that uses drivers-evergreen-tools to set up a cluster for local development as well as using the github action?

@aditi-khare-mongoDB

[baileympearson]

@aditi-khare-mongoDB Along with the changes in this PR, can you also put more context about the PR into the PR description? if/when Val reviews this PR, he likely won't understand why we're making these changes without additional context

[baileympearson]

A few small additional comments!

[baileympearson]

Now that we have tooling to run encryption tests using drivers-evergreen-tools - can we just use the same tooling in CI instead of using the github action?

[aditi-khare-mongoDB]

Good call!