Option to enable Ionospheric correction in INSAR_ISCE_TEST output

[jhkennedy]

DockerizedTopsApp has exposed an option to add Ionospheric correction layers when creating the GUNW product.

Enabling/disabling Ionospheric corrections is done via the --estimate-ionosphere-delay parameter, which takes true/false values, to the DockerizedTopsApp container HyP3 entry point. See ACCESS-Cloud-Based-InSAR/DockerizedTopsApp#74

This feature request is to add a new estimate_ionosphere_delay parameter to the INSAR_ISCE and INSAR_ISCE_TEST jobs with possible values of true and false.

E.g.,

{
  "job_type": "INSAR_ISCE",
  "job_parameters": {
    "granules": ["S1B_IW_SLC__1SDV_20210723T014947_20210723T015014_027915_0354B4_B3A9"],
    "secondary_granules": ["S1B_IW_SLC__1SDV_20210711T014947_20210711T015013_027740_034F80_D404"],
    "estimate_ionosphere_delay": "true",
  }
}

A job requested with "do_eds": "false" should produce the same output as currently produced, except the placeholder /science/grids/corrections/derived/ionosphere (typed as string) will be removed. If true is specified, the output NetCDF product should include a /science/grids/corrections/derived/ionosphere data layer.

[jhkennedy]

Bugfix for the container's --estimate-ionosphere-delay argument here: ACCESS-Cloud-Based-InSAR/DockerizedTopsApp#95

[jhkennedy]

I've updated #1446 to have separate tasks/issues for INSAR_ISCE_TEST, which was done in #1440, so I'm closing this one as done.