Fix sensor resource constraints removal to use replace instead of remove

The previous approach tried to remove the requests field, but the pod
still failed with insufficient CPU even after patching. This suggests
either the limits field was still present, or the remove operation
didn't work as expected with the Helm-deployed sensor.

New approach:
- Use JSON patch "replace" operation instead of "remove"
- Set entire resources field to empty object {}
- This removes both limits and requests in one operation
- Use kubectl rollout status to wait for deployment to complete
  instead of kubectl wait on pods (which fails when pods don't exist)

The replace operation is more reliable than remove when the structure
might vary (Helm vs direct deployment).

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: janisz

.github/workflows/smoke.yml

@@ -56,10 +56,12 @@ jobs:
 
       - name: Remove resource constraints from Sensor
         run: |
-          kubectl patch deployment sensor -n stackrox --type='json' -p='[{"op": "remove", "path": "/spec/template/spec/containers/0/resources/requests"}]'
+          # Replace resources with empty object to remove all limits and requests
+          kubectl patch deployment sensor -n stackrox --type='json' \
+            -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources", "value": {}}]'
 
-      - name: Wait for Sensor pods ready
-        run: kubectl wait --for=condition=ready --timeout=300s pod -l app=sensor -n stackrox
+          # Wait for the rollout to complete
+          kubectl rollout status deployment/sensor -n stackrox --timeout=300s
 
       - name: Extract Central password
         id: extract-password