Release v10.9.2

[jtherrmann]

TODO:

• Test new validation behavior
• Confirm two jobs submitted with same granules in different order give the same browse image: https://hyp3-test-api.asf.alaska.edu/jobs?user_id=jtherrmann&name=multi-burst-any-order

Confirmed I get the new Burst number + swath + polarization identifiers must be the same for reference scenes and secondary scenes when submitting mis-matched scenes to hyp3-test

Confirmed I can mix up the scene order when submitting to hyp3-test and pass validation, whereas validation fails in prod

Confirmed I can submit duplicate scenes to prod and pass validation, but I get the new Each reference scene must have a unique burst number + swath + polarization identifier error message when submitting to test.

[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?