1-2 to hour turnaround max for PR CI on ORFS

[oharboe]

trafficstars

Description

asap7 cva6 is an outlier.

https://jenkins.openroad.tools/job/OpenROAD-flow-scripts-Public/job/PR-3294-merge/2/pipeline-overview/?selected-node=195

Suggested Solution

Move longer running tests(say 1h30 cut-off) to a post-merge job, file github issues things break and prioritize fixing them instead of having 6+ hours turnaround for ORFS PRs.

If there is some build hardware that is several times slower than other build hardware, take it offline and put it to pasture?

Additional Context

No response