operator: move v1 nodepool tests to acceptance

This commit moves the v1 kuttl nodepool tests (aka with-flags) into the
acceptance suite. It additionally adds a test case for the vectorized
statefulset decommissioner which previously did not exist.

Author: chrisseto

.buildkite/testsuite.yml

@@ -213,49 +213,4 @@ steps:
         context: kuttl-v1
         report-slowest: 10
     soft_fail: true
-- group: Kuttl-V1-Nodepools Tests
-  key: kuttl-v1-nodepools
-  steps:
-  - agents:
-      queue: k8s-m6id12xlarge
-    command: ./ci/scripts/run-in-nix-docker.sh task ci:configure ci:test:kuttl-v1-nodepools
-    env:
-      LOG_LEVEL: trace
-      OTLP_DIR: /work/artifacts
-      OTLP_METRIC_INTERVAL: 5s
-    key: kuttl-v1-nodepools-run
-    label: Run Kuttl-V1-Nodepools Tests
-    notify:
-    - github_commit_status:
-        context: Kuttl-V1-Nodepools Tests
-    plugins:
-    - github.com/seek-oss/aws-sm-buildkite-plugin#v2.3.2:
-        json-to-env:
-        - secret-id: sdlc/prod/buildkite/github_api_token
-        - secret-id: sdlc/prod/buildkite/redpanda_sample_license
-        - secret-id: sdlc/prod/buildkite/slack_vbot_token
-    - https://[email protected]/redpanda-data/step-slack-notify-buildkite-plugin.git#main:
-        channel_name: kubernetes-tests
-        conditions:
-          branches:
-          - main
-          failed: true
-        message: ':cloud: Kuttl-V1-Nodepools Tests Job Failed'
-        slack_token_env_var_name: SLACK_VBOT_TOKEN
-    soft_fail: false
-    timeout_in_minutes: 30
-  - continue_on_failure: true
-    wait: null
-  - agents:
-      queue: pipeline-uploader
-    allow_dependency_failure: true
-    command: ""
-    key: kuttl-v1-nodepools-parse
-    label: Parse and annotate Kuttl-V1-Nodepools Tests results
-    plugins:
-    - github.com/buildkite-plugins/junit-annotate-buildkite-plugin#v2.4.1:
-        artifacts: work/operator/tests/_e2e_with_flags_artifacts/kuttl-report.xml
-        context: kuttl-v1-nodepools
-        report-slowest: 10
-    soft_fail: true
 

acceptance/features/helm-chart.feature

@@ -25,17 +25,12 @@ Feature: Redpanda Helm Chart
            enabled: true
            decommissionAfter: 15s
     ```
-    # May not be required?
-    # And Pods matching "app.kubernetes.io/instance=redpanda,app.kubernetes.io/name=foobar" are Ready
     When I stop the Node running Pod "bazquux-2"
+    # Wait for the Pod to get evicted from the stopped node.
     And Pod "bazquux-2" is eventually Pending
-    # This helps speed up the test and makes the following wait for Running to
-    # be less likely to assert on a phantom Pod.
-    # TODO: Something between these two steps is wrong. Pod transitions from
-    # Pending -> Terminating. Seems like a race between manual deletion and eviction?
-    # Maybe have the previous step block until the Node is actually registered as dead?
-    # And I force delete Pod "bazquux-2"
+    # Observe that it gets rescheduled.
     Then Pod "bazquux-2" will eventually be Running
+    # And showcase that ghost brokers have been pruned.
     And kubectl exec -it "bazquux-0" "rpk redpanda admin brokers list | sed -E 's/\s+/ /gm' | cut -d ' ' -f 1,6" will eventually output:
     ```
     ID MEMBERSHIP