fix: increase chains timeout since we're hitting worst case

* 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 timeouts 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, one option, by shifting the checks to
  execute on the staging cluster instead, which has
  comparatively less load.

Signed-off-by: Dheeraj<[email protected]>

pkg/constants/constants.go

@@ -155,8 +155,9 @@ const (
 
 	PipelineRunPollingInterval = 10 * time.Second
 
-	// Increased to 30 min from 10 min due to https://issues.redhat.com/browse/KFLUXBUGS-24
-	ChainsAttestationTimeout = 30 * time.Minute
+	// Increased to 1.5 hrs from 10 min due to https://issues.redhat.com/browse/KFLUXBUGS-24,
+	// and since now we're frequently hitting the worst case
+	ChainsAttestationTimeout = 90 * time.Minute
 
 	JsonStageUsersPath = "users.json"