OGV Governance Fork test improvement

With the implementation of Oracle Router's recency checks on Oracle prices, our fork test environment no longer processes fork network blocks & time for the amounts configured on the mainnet to pass proposals. We have rather modified the deploy scripts to shorten the proposal voting and queue times.

But this doesn't solve all the issues. Currently, there is a problem with the 060 deploy. The proposal has been submitted on the mainnet and queued. The deploy scripts rightly shorten the voting and queue time on the contract but the proposal has already been queued on the mainnet before the queue time has been shortened on the forked environment that bases off of the mainnet.

Possible solutions:

1. find a hackish way by modifying storage slots to change the queue time of an active proposal
2. cancel queued proposal and re-submit it, vote for it and queue & execute it
3. alter Oracle router so that on the forked network the data can be stale and tests will pass. -> can't really test oracle data recency then

I'd vote for option 2.

Start by reviewing the fork test environment and deploy scripts, then reproduce the 060 deployment against the queued mainnet proposal. Compare the three proposed approaches and verify that the chosen approach lets fork governance proposals complete while preserving Oracle Router recency checks.