The Stage periodic CI is failing due to the SC bootstrap test not being compatible with the new dormant Service Cluster logic.

The test currently polls for the SC to reach ready status, but under the new behavior, a newly provisioned SC may transition to maintenance in <1 minute. This means the test may never observe the SC in ready, resulting in a timeout:

23:01:44   [FAILED] Timed out after 1200.014s.
23:01:44   Expected
23:01:44       <string>: maintenance
23:01:44   to equal
23:01:44       <string>: ready
23:01:44   In [It] at: /var/lib/jenkins/workspace/osdfm-periodic-ci-tests-stage/cases/osdfm/cluster_bootstrap_test.go:107 @ 12/08/25 23:01:44.484 

To make the CI flow stable again, the test should no longer depend on observing ready status within a specific window. Instead, similar to dormant CI behavior, the test can reliably validate: The provision shard reference (PS) is non-empty, and The SC has transitioned into maintenance, which implicitly guarantees it reached ready beforehand. This change will make the Stage CI deterministic under the new autoscaling and dormant-SC workflow.

🎯 Acceptance Criteria
SC bootstrap test no longer checks for ready state directly. Test validates SC readiness indirectly using: Non-empty provision shard reference (PS) SC status = maintenance Stage periodic CI succeeds consistently under dormant-SC logic. No regression in INT or Stage bootstrapping flows.