Fold multiple integration test cases into the complex test case

[rifelpet]

Each integration test case adds many LoC and some overhead in running the integration tests.

Since many of the tests are only testing a specific feature, it would be simpler to combine all of the non-mutually exclusive features into the single complex case. We could probably do this to more of the test cases but this was my first high level pass.

WIP while I figure out this test failure. hack/verify-expected.sh reports that it found a difference and wrote it to the files but there aren't any actual changes to the file afterwards...

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[rifelpet]

oh, i remember this happening before. its because we run 3 test cases for complex and one of them changes the file to one thing and a later test (looks like the legacy apiVersion test) changes it back. end result is the same incorrect file. ill see if i can split that up somehow.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rifelpet]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/lgtm