Sleep timeout for github builds too short

[cdce8p]

Over at setup-python I noticed that builds didn't get triggered as they should have been. https://github.com/actions/python-versions/pull/350#issuecomment-3191278175

Turns out the trigger Github builds step always aborts as it can't find the triggered CI run and thus doesn't schedule the second build. https://github.com/actions/python-versions/actions/runs/16979660706/job/48136808507#step:3:13

If I had to guess, I'd say the sleep timeout with 10s is too short. Increasing it to 60 or even 120 should do the trick. https://github.com/actions/versions-package-tools/blob/13ba3fd9e01a4cc04e870994d1e42e6eb51d6587/github/run-ci-builds.ps1#L70-L78

Overall, waiting 1min between triggered builds shouldn't be a big deal. With it failing, it waits for the next schedule run which is usually 12h away.

Thus adjusting it will fix the issue and decrease the workload on staff as they don't have to manually trigger the builds again / approve multiple manifest update PRs.