feat(CI): add timeout to CI

[tcoratger]

Should resolve #4727.

[codecov]

Codecov Report

Merging #4728 (0bd9cb7) into main (e83d3aa) will decrease coverage by 0.02%.
Report is 3 commits behind head on main.
The diff coverage is n/a.

see 12 files with indirect coverage changes

Flag	Coverage Δ
integration-tests	16.55% <ø> (+<0.01%)	⬆️
unit-tests	63.56% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
reth binary	32.17% <ø> (ø)
blockchain tree	83.73% <ø> (ø)
pipeline	88.53% <ø> (ø)
storage (db)	73.70% <ø> (ø)
trie	94.73% <ø> (-0.04%)	⬇️
txpool	49.82% <ø> (ø)
networking	77.14% <ø> (-0.06%)	⬇️
rpc	57.86% <ø> (-0.01%)	⬇️
consensus	63.09% <ø> (ø)
revm	28.33% <ø> (ø)
payload builder	8.32% <ø> (ø)
primitives	86.51% <ø> (-0.04%)	⬇️

[DaniPopes]

Can we add these to tests workflows too?

[tcoratger]

Can we add these to tests workflows too?

@DaniPopes Yes sure, I've just extended, tell me if this is better or if you see other places with this should be set like that? For me this seems good like that, I've pushed the timeout to 60 minutes at the most critical places.

[DaniPopes]

It's missing integration.yml I think then we're good
Also a tip @tcoratge use "resolve" or similar keywords so the issue gets automatically closed on merge: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests

[tcoratger]

It's missing integration.yml I think then we're good Also a tip @tcoratge use "resolve" or similar keywords so the issue gets automatically closed on merge: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests

Done, thanks for the tip, I don't know why I was thinking that "solve" did the same job but I should have checked if the issues closed automatically...