Configure timeout-minutes for GH actions which run Maestro tests

[CDRussell]

Task/Issue URL: https://app.asana.com/0/608920331025315/1209118297419133/f

Description

Adds timeout-minutes to all the steps which are triggering a Maestro test run on Robin.

• we want timeouts to be treated as a failure, not for the CI to give up on a timeout and report as a success
• configuring the timeouts this way gives us genuine timeouts that will fail the build if the timeout-minutes value is exceeded for that step.

Steps to test this PR

• QA optional
• From a manual test, i confirmed using this approach will successfully time out and fail the build if the Robin tests take too long to run 👇

[CDRussell]

• Configure timeout-minutes for GH actions which run Maestro tests #5554 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[malmstein]

small nit on the variable

[malmstein]

nit: since we are using the same value for all different workflows, how would you feel about adding this value as a Variable? project-id: ${{ vars.ROBIN_TIMEOUT_MINUTES }}

[CDRussell]

Good idea. Assuming there won't be any issues with it thinking it’s now a string instead of an int?

We’ll find out. 😄

[CDRussell]

Did a test run; seems fine