Failures in e2e tests can cause GitHub workflows to run for maximum duration

[hasheddan]

What did you do?

I noticed in a recent e2e workflow run that it ran for 6 hours before ultimately being canceled. It appears this was due to an intermittent issue, but the failure caused the test to never end.

What did you expect?

I expected a failing e2e test to run to completion.

Assigning myself here to hunt down the issue, but we should also likely reduce the max workflow run time.

[daenney]

The workflows are synced from here: https://github.com/pion/.goassets/tree/master/ci/.github/workflows and the reusable ones in https://github.com/pion/.goassets/tree/master/.github/workflows. We should set timeouts on the flows there honestly. Most test runs, I think even for other things in the Pion org, are expected to run in 5-10min tops.

The e2e.yaml in this repo is unique to this repo, so you can set a timeout on that one directly by plonking a https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes in it.