fix(ui): Disable GKE Metadata as default Fixes: #11247, fixes #11260

[dvcanton]

Description of your changes:

• UI presents errors when deployed outside GKE as pointed in [frontend] Error on Kubeflow Pipelines Dashboard: 'No Healthy Upstream', '503 UC upstream_reset_before_response_started{connection_termination}' #11260.
• DISABLE_GKE_METADATA was set true as default and patched for GKE environments
• Tests were also adjusted

Fixes: #11247 & #11260

Duplicated from #11321 to include tests.

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zijianjoy for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• frontend/OWNERS
• manifests/kustomize/OWNERS

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

[google-oss-prow]

Hi @dvcanton. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[hbelmiro]

@dvcanton can you take a look at the failing tests?

[dvcanton]

Hi @hbelmiro, thanks for the heads up. I have looked into the frontend server tests. They all pass locally now.

Test Suites: 10 passed, 10 total
Tests:       128 passed, 128 total
Snapshots:   12 passed, 12 total
Time:        8.185s, estimated 9s
Ran all test suites.