fix(STONEBLD-2265): increase chains timeout since chains controller is overwhelmed

[dheerajodha]

Description

• Because the build-definitions PR checks are running on the production cluster, due to the heavy load chains controller is overwhelemed more often.
• This is causing test timeout while waiting for chains controller to attest artifacts.
• These days, we're hitting the worst case more often making it difficult for us to merge PRs on build-def repo.
• This PR increases the timeout from 30 mins to 90mins
• We should reduce this timeout as soon as the situation is improved by shifting the checks to execute on the staging cluster instead, which has comparatively less load.

Issue ticket number and link

STONEBLD-2265

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
• I have updated labels (if needed)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[tisutisu]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MartinBasti, tisutisu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tisutisu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[MartinBasti]

/retest-required

[openshift-ci]

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

• ➡️ [failed] [It] [jvm-build-service-suite JVM Build Service E2E tests] when the Component with s2i-java component is created a PipelineRun is triggered [jvm-build, HACBS]

Expected success, but got an error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    {}

---

@dheerajodha: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/redhat-appstudio-e2e	0fd94e0	link	true	/test redhat-appstudio-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[psturc]

the last CI run failed on known issue

I think we can force-merge this PR, wdyt @MartinBasti @dheerajodha ?

[MartinBasti]

fine by me to merge it