Merge INSAR_ISCE_MULTI_BURST into INSAR_ISCE_BURST

[jtherrmann]

Jira: https://asfdaac.atlassian.net/browse/TOOL-3166

Note: The above link is accessible only to members of ASF.

---

Currently we have an INSAR_ISCE_MULTI_BURST job spec (which takes reference and secondary parameters) and a separate INSAR_ISCE_BURST job spec (which takes a granules parameter) because it was the easiest way to merge the multi-burst work to main without breaking backwards compatibility for INSAR_ISCE_BURST.

When we're ready to break backwards compatibility by replacing the granules parameter, we'll need to:

• Rename INSAR_ISCE_MULTI_BURST.yml to INSAR_ISCE_BURST.yml (replacing the existing INSAR_ISCE_BURST.yml)
• Rename the job type to INSAR_ISCE_BURST (first line of the job spec)
• Remove INSAR_ISCE_MULTI_BURST.yml from hyp3-multi-burst-sandbox deployment
• Currently the validate_jobs function calls convert_single_burst_jobs to convert the parameters for all INSAR_ISCE_BURST jobs from granules to reference and secondary in validation.py. This can be removed, along with any test cases for the granules parameter for insar burst jobs.
• Rename INSAR_ISCE_MULTI_BURST to INSAR_ISCE_BURST everywhere it's used in the code (see git grep INSAR_ISCE_MULTI_BURST); should just be set_batch_overrides.py, test_set_batch_overrides.py, and test_validation.py
• Update the parameters in all old INSAR_ISCE_BURST job records, so that interacting with existing jobs does not break; this will need to be done for test deployments as we merge to develop, and then for prod deployments as we merge to main