PHPLIB-950: Run legacy CSFLE tests on serverless

[alcaeus]

PHPLIB-950

Includes fixes required to get CSFLE running on Serverless in general:

• Needs mongocryptd or crypt_shared installed
• Needs secrets exported
• Needs KMS servers running

The download logic was shamelessly copied from the GO driver, as this isn't available through drivers-evergreen-tools. I've created DRIVERS-2459 to track this and will take a look when possible.

[jmikola]

AFAIK, we don't run serverless tests for PR builds. Please schedule an Evergreen patch build that includes the serverless task(s) and attach it to this PR so we can confirm that all works before merging.

[jmikola]

IIRC, this is handled by run-orchestration.sh in drivers-evergreen-tools for non-serverless tests. That appears to be exactly what DRIVERS-2459 is meant to address.

IMO, this should have been addressed as a prerequisite for DRIVERS-2400 before spawning language tickets and inviting drivers to sort this out on their own.

[jmikola]

None of the commits in this PR indicate the sync target for spec tests. According to DRIVERS-2400 this is mongodb/specifications@59a07b7. Please add that and ensure it ends up in the final squash message.

[alcaeus]

Ah, yes. Added to the last commit and will make sure it ends in the squash message.

[alcaeus]

AFAIK, we don't run serverless tests for PR builds. Please schedule an Evergreen patch build that includes the serverless task(s) and attach it to this PR so we can confirm that all works before merging.

Sorry for not mentioning that above. I scheduled a patch build already: https://evergreen.mongodb.com/build/mongo_php_library_serverless__php_edge_versions~latest_stable_driver_versions~latest_stable_os~debian11_patch_8a327525dbb4a2a9bceac62bfc027e88309db756_633d6772a4cf4706e978aee3_22_10_05_11_16_03?redirect_spruce_users=true

Note that scheduling an additional task in a PR build has the advantage of making the required evergreen check fail if the additional task fails, which in turn prevents a merge of the PR. Only downside is that this has to be done every time after pushing changes, as that will trigger a new evergreen patch build discarding the previously selected tasks.