Release v7.10.0

[jtherrmann]

TODO:

• [x] Validate in hyp3-test and hyp3-enterprise-test
• [x] Consider whether the step function changes warrant draining the job queue before merging
  • I don't think so, because this doesn't match the scenario described below (see the review checklist comment).

hyp3-test validation jobs: https://hyp3-test-api.asf.alaska.edu/jobs?user_id=jtherrmann&name=jth-20241001-multi-burst-changes

• All jobs used expected memory values
• 6/8 jobs succeeded (the AUTORIFT S1 and Landsat jobs weren't expected to succeed)

hyp3-enterprise-test validation jobs: https://hyp3-enterprise-test.asf.alaska.edu/jobs?user_id=jtherrmann&name=jth-20241001-multi-burst-changes

• All jobs used expected memory values
• 10/10 jobs succeeded

Post-release:

hyp3 validation jobs: https://hyp3-api.asf.alaska.edu/jobs?user_id=jtherrmann&name=jth-20241001-multi-burst-changes

• All jobs used expected memory values
• 6/6 jobs succeeded

[github-actions[bot]]

Developer checklist

• [x] 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
• [x] (If applicable) Updated the dependencies and indicated any downstream changes that are required
• [x] Added/updated documentation for these changes
• [x] Added/updated tests for these changes
• [x] 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?