1. 1. Summary

Sets `presign_duration: 168h` (the S3 maximum of 7 days) on the `custom_build_deliver` `s3.put` that uploads the custom build dist tarball to the consumer bucket. Uses the new Evergreen `s3.put` parameter from evergreen-ci/evergreen#10725 (DEVPROD-42333): the configured duration is stored with the artifact and applied whenever the lazy artifact endpoint generates a presigned URL, so the Files-tab link handed to a consumer's support contact stays valid for a work week instead of the default.

Constraints inherited from the Evergreen change, both satisfied here: `presign_duration` requires `visibility: signed` and static AWS credentials (this upload uses the `aws_key_build`/`aws_secret_build` project variables, not `role_arn`/assumed roles).

Notes:

• Textual-conflict heads-up with #62189, which touches the same `s3.put` and adds a manifest upload next to it; whichever merges second resolves trivially, and the manifest `s3.put` should get the same `presign_duration` at that point.
• Backport to v8.0 (where the Splunk variants actually run) will follow once this and #62190 settle.

1. 1. Testing

• `evergreen validate p mongodb-mongo-master etc/evergreen_nightly.yml`: same 36 pre-existing `release*` distro-allowlist errors as unmodified master and nothing else — i.e. the production validator accepts `presign_duration`, confirming the Evergreen change is deployed.