Bump promote_to_epic query threshold for flaky spec
What does this MR do?
Raises the query-limiting threshold in the promote_to_epic GraphQL mutation request spec from 141 to 150 for the "when user can create epic in new group" example.
The threshold here is an acknowledged temporary workaround for the epic-work item sync migration. The query count during promotion is non-deterministic: in job https://gitlab.com/gitlab-org/gitlab/-/jobs/15256990524 the same example executed 142 queries on the initial run and 147 on the fail-fast retry within a single CI job, depending on cold vs. warm per-process caches. Both exceed the previous threshold of 141, causing flaky failures.
150 keeps margin above the observed maximum until the query reduction is handled as part of the epic-work item sync cleanup.
References
- Broken job: https://gitlab.com/gitlab-org/gitlab/-/jobs/15256990524
- Follow-up (restore threshold after epic-work item sync): #438295
Edited by Stan Hu