HyP3 v9.5.3

Fixed

• When the API returns an error for an INSAR_ISCE_BURST job because the requested scenes have different polarizations, the error message now always includes the requested polarizations in the same order as the requested scenes (previously, the order of the polarizations was not guaranteed). For example, passing two scenes with VV and HH polarizations, respectively, results in the error message: The requested scenes need to have the same polarization, got: VV, HH
• The API validation behavior for the INSAR_ISCE_MULTI_BURST job type is now more closely aligned with the CLI validation for the underlying HyP3 ISCE2 container. Currently, this only affects the hyp3-multi-burst-sandbox deployment.
• The requested scene names are now validated before DEM coverage for both INSAR_ISCE_BURST and INSAR_ISCE_MULTI_BURST.
• The lambda_logging.log_exceptions decorator (for logging unhandled exceptions in AWS Lambda functions) now returns the wrapped function's return value rather than always returning None.
• Ruff now enforces that all functions and methods must have type annotations.
• Updated the DIST-S1 entrypoint of the image and changed the job spec accordingly.