The Evergreen project configuration contains several instances of hard-coded values in the remote_file parameter of s3.put commands. This was okay when there was a single Evergreen project associated with the repository and when releases were made directly from the master branch. However, we now have three Evergreen projects associated with the repository, releases made from release-specific branches, and a project specifically for tracking work done on feature branches.

The specific instances that need to be addressed are occurrences of libmongocrypt that should be replaced with ${project} and occurrences of master that should be replaced with ${branch_name}. These are located in the s3.put commands of the upload-java and upload-all tasks. Similar values in the windows-upload and debian-package-build tasks may not necessarily need to be changed, but rationale for hard-coded values should be included in a comment.

Changes to these values should be made in such a way as to ensure that workflows that depend on the affected artifacts (e.g., downstream driver projects) are not broken.