Allow running OPERA_RTC for older granules that have been re-processed with newer IPF version

[jtherrmann]

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

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

---

Our initial plan for the OPERA_RTC job type was to check IPF version for each granule's CMR metadata directly, and disallow granules with IPF version less than 002.70. We removed this implementation in e2f2bfa because it is blocked by #2737. That is, the implementation assumed that the granule's CMR metadata was given as umm_json which includes IPF version (e.g. like this) but it is actually given as json (e.g. like this).

We opted to simply disallow granules older than 2016-04-14, given that https://sar-mpc.eu/processor/ipf/ shows 2016-04-13 12:00:00 as the latest "end usage" date for an IPF version older than 002.70. However, according to @asjohnston-asf here:

Here's the IPF distribution of all S1A SLCs acquired before 2016-03-31. 26% have IPF >= 002.70.

so there could be a decent number of older granules that have been re-processed with a newer IPF version. Ideally we would probably allow running OPERA_RTC on those granules by checking the IPF version directly, as described above.