WIP: open firewall to allow gcp health probes

[patrickdillon]

We are seeing capg-based e2es fail with:

 [Jira:"Networking / router"] monitor test service-type-load-balancer-availability setup expand_less 	11m17s
{  failed during setup
could not reach http://34.170.127.198:80/echo?msg=hello reliably: timed out waiting for the condition}

This attempts to open firewalls to allow GCP health probes to access the nodes. Currently, though, in testing, it has not worked in resolving the issue. Leaving this as a reference.

Depends on #8314 to be able to complete install and run e2e

[openshift-ci]

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

[patrickdillon]

/label platform/gcp

[openshift-ci]

@patrickdillon: The label(s) /label platform/gcp cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label platform/gcp

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.

[bfournie]

/label platform/google

[bfournie]

I think this fix is still reasonable and consistent with Terraform firewall rules even though it wasn't necessary to resolve the e2e issue.