feat: add a new global library 'withRetryAndTimeout' to allow circuit breaking pipeline steps

[dduportal]

This PR provide a circuit breaker of type "retry with timeout per retry" library.

Its initial case it to ensure that some of the jenkins-infra's docker builds involving network operations were not blocking (e.g. 10 min timeout before failing the step), but retrying a few times before really failing the job.

Ref. https://issues.jenkins.io/browse/JENKINS-51454

Please note that there are incoming PRs on the Jenkins Pipeline-related plugins that would allow using pure retry and timeout methods instead of try/catch: the library would have to be reconsidered or updated and better tested at this moment.

Another added value of this library: an environment variable PIPELINE_RETRY_COUNTER is injected to hold the retry counter's values (e.g. "how many retries?"). This value can be used by consumer to identify uniquely some resources such as warning-ng reports.

[timja]

seems sensible? any other thoughts?

[dduportal]

@timja I'm confused by the compiler error messages (I got the same locally).
I understand that the exceptions types are not known by the Eclipse Groovy compiler: in real life it works as expected (see. jenkins-infra/docker-jenkins-weeklyci#208) but not in the build/test environment.

Should we add the hpi plugins of the workflow steps (which provides timeout and the exception types) as part of the build/test dependencies here? Or did I miss something?

[jglick]

see jenkinsci/workflow-basic-steps-plugin#144

[dduportal]

see jenkinsci/workflow-basic-steps-plugin#144

@jglick Should I look at this change as a FYI, or is it related to the dependency question (or something else)?

[timja]

see jenkinsci/workflow-basic-steps-plugin#144

@jglick Should I look at this change as a FYI, or is it related to the dependency question (or something else)?

it means we wouldn't need this PR at all

[dduportal]

Fair, given that the linked PR is "almost there" (modulo the GitHub incident/ end of approval window / merge / release), I'll go back to the road of "try catch on pipeline with approved call to causes" on the few repositories (https://github.com/jenkins-infra/docker-jenkins-weekly/ and https://github.com/jenkins-infra/docker-jenkins-lts) which requires the change right now. Thanks a lot for taking time to review and give advises on this!