fix(ci): increase deploy wait timeout

[dcaravel]

Increase the scanner deploy wait timeout even longer (was bumped to 10m here: #1835)

CI in the release-2.35 branch has been failing, in the latest run scanner was in the middle of loading /nvd_definitions:

{"Attempt":3,"Event":"Retrying connection to DB","Level":"warning","Location":"database.go:83","Time":"2025-05-09 15:05:42.427486"}
{"Event":"running database migrations","Level":"info","Location":"pgsql.go:198","Time":"2025-05-09 15:05:52.996493"}
{"Event":"database migration ran successfully","Level":"info","Location":"pgsql.go:205","Time":"2025-05-09 15:05:53.273058"}
{"Event":"Loading NVD definitions into cache","Level":"info","Location":"singleton.go:24","Time":"2025-05-09 15:10:49.985059"}
{"Event":"Loading definitions directory","Level":"info","Location":"load.go:19","Time":"2025-05-09 15:10:49.985196","dir":"/nvd_definitions"}

When the job was failed due to timeout:

**** 15:10:03: ERROR: pre test failed

[dcaravel]

Second thought - the timeout in most recent failure may be different - double-checking

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-stackrox-scanner-release-2.35-merge-e2e-tests/1920634416435040256

error: timed out waiting for the condition on pods/scanner-777c6c7976-8jgjs
subprocess.CalledProcessError: Command '['scripts/ci/deploy.sh', 'deploy']' returned non-zero exit status 1.

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-stackrox-scanner-release-2.35-merge-e2e-tests/1920835464898547712)

subprocess.TimeoutExpired: Command '['scripts/ci/deploy.sh', 'deploy']' timed out after 600 seconds

[openshift-ci]

@dcaravel: 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/e2e-tests	3c757d5	link	false	/test e2e-tests

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-sigs/prow repository. I understand the commands that are listed here.