[Bug]: Orbit file staging script needs to apply 60 minute start time margin to SAFE start time

[collinss-jpl]

Checked for duplicates

Yes - I've already checked

Describe the bug

A recent change to the s1_reader library has added a requirement that orbit files start at least 60 minutes prior to the start time of the corresponding SLC SAFE archive. The PCM orbit file staging script needs to be updated to enforce the same requirement.

What did you expect?

For a specific granule (S1A_IW_SLC__1SDV_20230621T234548_20230621T234607_049091_05E73D_5956), the orbit staging script needs to select S1A_OPER_AUX_POEORB_OPOD_20230711T080815_V20230620T225942_20230622T005942.EOF (orbit start time is 60+ minutes prior to SAFE start time) as the orbit file for use with the job, rather than S1A_OPER_AUX_POEORB_OPOD_20230712T080728_V20230621T225942_20230623T005942.EOF.

Reproducible steps

Submit a PCM job with the S1A_IW_SLC__1SDV_20230621T234548_20230621T234607_049091_05E73D_5956 granule as trigger. The triggered RTC and CSLC jobs should fail since the orbit file will be incorrect.

Environment

- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...