Remove openshift-sdn-based CI jobs by 4.17 (origin)

openshift-sdn is no longer supported for new installs as of 4.15, and it will be completely removed from OpenShift in 4.17.

Your component currently has one or more CI jobs that use openshift-sdn:

ci-operator/config/openshift/origin/openshift-origin-master.yaml
  e2e-aws-multitenant
  e2e-metal-ipi-sdn
  e2e-metal-ipi-serial

These jobs will need to be removed or migrated to ovn-kubernetes by OCP 4.17. In some cases, if you were not intentionally testing openshift-sdn, it may make sense to start migrating these jobs in 4.15. You may want to split this bug into multiple bugs for different OCP versions.

Component-specific notes:

• origin uses the common pattern of testing baremetal with sdn+ipv4 (e2e-metal-ipi-sdn) and ovn+ipv6 (e2e-metal-ipi-ovn-ipv6). Depending on your testing needs, it may make sense to remove the sdn+ipv4 job and keep just the ovn+ipv6 one, or to replace the sdn+ipv4 job with ovn+ipv4, or to replace both jobs with a single ovn+ipv4 job.
• It follows the same pattern with serial tests, doing sdn+ipv4 (e2e-metal-ipi-serial) and ovn+ipv6 (e2e-metal-ipi-serial-ovn-ipv6). Similar considerations apply.
• e2e-aws-multitenant is presumably there so we can test changes to multitenant-specific e2e tests, so it should stick around for now, I guess. It's optional but should probably also be not-run_always?