test: update ch version in tests, multiple changes for e2e stabilizat…

[GrigoryPervakov]

Why

e2e tests in the CI are flaky

What

• Add deadline and retries to the version-probe jobs
• Increase timeouts in the keeper e2e and simplify timeout tracking
• Stabilize OpenShift tests by increasing timeouts and waiting for APIService; build only needed platform
• Increase scorecard's bundle timeout
• Upgrade ch versions in tests and pin the exact minors
• Use per-job go cache artifact keys
• Switch to an Alpine Docker image to speed up image build as it already contains ca-certs
• Set explicit timeouts, permissions, and actions SHA in the workflows
• Add CodeQL workflow
• Retry ClickHouse image pre-pulls
• Cancel superseded PR runs via concurrency groups (frees self-hosted runners)
• Dockerfile: drop go build -a, add BuildKit cache mounts for incremental image rebuilds

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.