Remove enabling multinetwork policy

[trozet]

This is now enabled by default in aws serial jobs:

openshift/release#41872

[trozet]

/retest-required

[tssurya]

/retest

[tssurya]

ideally speaking we don't have to do this PR since this is required only when we run this test in lanes that doesn't have multi-network policy enabled by default right? -> like its no-op in aws-serial lane, but tomorrow if we add this test to other non-aws-serial lanes, then we need to manually enable this flag via test so wondering it there is use in just leaving this as is? Or folks have to be careful to not add this test to any of the non-aws-ovn-serial lanes because those lanes don't have this feature enabled by default.
EDIT:
if we do decide to keep this stuff we should fix the wait part for CNO

[ricky-rav]

I think the easiest thing is to remove the enabling/disabling part and leave a comment saying that this test expects the multi network policy feature to be enabled in the cluster and we don't want to enable it only for the duration of this test, since the resulting CNI rollout could cause unexpected behaviour in the tests that follow, as we've seen already. Also, waiting for the whole ovnk rollout to complete would mean stalling for ~12 minutes... twice (for ipv4, and for ipv6), if not 4 times, if we also want to wait for the rollout that enables the feature :)

[trozet]

ideally speaking we don't have to do this PR since this is required only when we run this test in lanes that doesn't have multi-network policy enabled by default right? -> like its no-op in aws-serial lane, but tomorrow if we add this test to other non-aws-serial lanes, then we need to manually enable this flag via test so wondering it there is use in just leaving this as is? Or folks have to be careful to not add this test to any of the non-aws-ovn-serial lanes because those lanes don't have this feature enabled by default. EDIT: if we do decide to keep this stuff we should fix the wait part for CNO

we still need the PR cause the test case tries to disable the feature as well

[ricky-rav]

/retest

[tssurya]

/lgtm
wohoo tests are passing now?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: trozet, tssurya

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:

• test/extended/networking/OWNERS [trozet]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 6ee9dc5 and 2 for PR HEAD 42780d1 in total

[openshift-ci]

@trozet: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-ovn-rt-upgrade	42780d1	link	false	/test e2e-gcp-ovn-rt-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.