Add timeout to main build (#322)

[beatngu13]

Proposed commit message:

Add timeout to main build (#322)

According to #322, the main build occasionally times out. Until
further investigation, this PR will add a timeout to the main build.

PR: #323

Note that I didn't close the corresponding issue on purpose. Maybe we want to rephrase it because I think we are better off investigating why the build actually runs forever. The added timeout only addresses a sympton, not the disease.

---

PR checklist

The following checklist shall help the PR's author, the reviewers and maintainers to ensure the quality of this project.
It is based on our contributors guidelines, especially the "writing code" section.
It shall help to check for completion of the listed points.
If a point does not apply to the given PR's changes, the corresponding entry can be simply marked as done.

Documentation (general)

• There is documentation (Javadoc and site documentation; added or updated)
• There is implementation information to describe why a non-obvious source code / solution got implemented
• Site documentation has its own .adoc file in the docs folder, e.g. docs/report-entries.adoc
• Only one sentence per line (especially in .adoc files)
• Javadoc uses formal style, while sites documentation may use informal style (see Documentation: Personal or formal style #265)

Documentation (new extension)

• The docs/docs-nav.yml navigation has an entry for the new extension
• The package-info.java contains information about the new extension

Code

• Code adheres to code style, naming conventions etc.
• Successful tests cover all changes
• There are checks which validate correct / false usage / configuration of a functionality and there are tests to verify those checks (see Require configuration failiure tests? #164)
• Tests use AssertJ or our own PioneerAssert (which are based on AssertJ)

Contributing

• A prepared commit message exists
• The list of contributions inside README.md mentions the new contribution (real name optional)

---

I hereby agree to the terms of the JUnit Pioneer Contributor License Agreement.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
No Duplication information

[Bukama]

Note that I didn't close the corresponding issue on purpose. Maybe we want to rephrase it because I think we are better off investigating why the build actually runs forever. The added timeout only addresses a sympton, not the disease.

I think it's okay to do this seperated and first kill the sympton to don't block resources too long. I think to define a well chosen timeout even when there are no known issues is fine. Meaning we can and should close the issue ans the issue is about defining a timeout. Investigate and fix the issue of the timeouting build is another thing and we should not mix issues.

[aepfli]

LGTM

[aepfli]

i do understand both sides regarding issue, and i am fine with both - so @Bukama and @beatngu13 as soon as you agreed on that, either merge or let me know and i will merge :)

[beatngu13]

I'm all good with @Bukama's suggestions. Well-chosen timeouts are indeed sensible*, I just wanted to emphasize that we have to dig deeper to find out what's actually the issue. I don't care if we create one, two or more issues for that. ✌️

*: Should we add them to the other workflows as well?