Release v10.17.4

[asjohnston-asf]

TODO before merging:

• delete the manually-created GitHub identity provider in the edc-prod account
• deploy the CI stack to the edc-prod account
• delete the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY secrets from the edc-prod github environment
• add the AWS_ROLE_ARN secret to the edc-prod github environment

UAT deployment via OIDC succeeded: https://github.com/ASFHyP3/hyp3/actions/runs/27990921071
UAT verification job succeeded: https://hyp3-test-api.asf.alaska.edu/jobs/779b9649-8a95-473c-ac31-4dbe4015d373
UAT API access logging continues to work as expected.

[github-actions]

Developer checklist

• Indicated the level of changes to this package by affixing one of these labels:
  • major -- Major changes to the API that may break current workflows
  • minor -- Minor changes to the API that do not break current workflows
  • patch -- Patches and bugfixes for the current version that do not break current workflows
  • bumpless -- Changes to documentation, CI/CD pipelines, etc. that don't affect the software's version
• (If applicable) Updated the dependencies and indicated any downstream changes that are required
• Added/updated documentation for these changes
• Added/updated tests for these changes
• Verified changes in test deployment and summarized results, e.g. in PR description or comments on the related issue(s)
• If the step function code has changed, have you drained the job queue before merging?
  • For example, if the interface for a Lambda function has changed to expect different input,
    then currently running jobs (which use the old step function definition) will call the new
    function with the old input. So we must drain the job queue before deployment, so that the new
    function is only called by the new step function definition.

Reviewer checklist

• Have all dependencies been updated?
• Is the level of changes labeled appropriately?
• Are all the changes described appropriately in CHANGELOG.md?
• Has the documentation been adequately updated?
• Are the tests adequate?
• Have the changes been verified in the test deployment?