exit successfully with no changes when run via hyp3 with weather_model=HRRR and outside HRRR coverage

[asjohnston-asf]

Pivoting to a shorter-term change than #695 , I believe this is sufficient to let ASF provide standard ARIA_S1_GUNW products on demand via HyP3. Standard Jobs will always be submitted with weather_model=HRRR. Jobs within HRRR coverage will have the data layers added. Jobs outside HRRR temporal or spatial coverage will exit successfully without making any changes to the GUNW file.

The only invocation of the changed check_weather_model_availability function is at https://github.com/dbekaert/RAiDER/blob/dev/tools/RAiDER/cli/raider.py#L633 , which is only called when processing via HyP3. Returning false instead of raising an exception allows the program to exit successfully after doing nothing, as desired by HyP3, rather than existing with an error code after doing nothing.

Expanding the logic for a weather model for a standard product in the future, say to add the use of additional weather models, would require more in-depth changes such as those in #695.

[asjohnston-asf]

@cmarshak @jhkennedy I believe this one line change is sufficient to let ASF produce standard products on-demand and make the correct weather model choice on the user's behalf. Are you (or others) available to review and merge to dev? That would let ASF validate the changes end-to-end in one of our non-production HyP3 environments.

I'll take a stab at resolving ACCESS-Cloud-Based-InSAR/DockerizedTopsApp#191 today or tomorrow if that helps take something off the ARIA's team plate, since ASF will also need that fix for an end-to-end test.

[cmarshak]

Nice work including the added tests and test data. I think this is ready to be merged and released.

[cmarshak]

Thanks for including this.