glooctl checking virtual services depends on checking upstreams

[nfuden]

Gloo Edge Version

1.14.x (beta)

Kubernetes Version

None

Describe the bug

When glooctl is run with the exclude upstreams flag it will error on virutal services that refer to any upstreams.

User will see something like: `Error: 2 errors occurred:

• Virtual service references unknown upstream: (Virtual service: gloo-system json-to-grpc | Upstream: gloo-system default-bookstore-8080)
• xds metrics check was skipped due to an error in checking deployments`

Steps to reproduce the bug

1. Setup a valid vs that points to a valid us (follow any example)
2. glooctl check | grep error should find nothing
3. gloocl check --exclude deployments,upstreams,rate-limit-configs,secrets,auth-configs | grep error finds error...

Expected Behavior

glooctl at worst warns on vs if skipping upstream checks or warns that the check could be incomplete but should not throw an error.

Additional Context

When debugging in a simple environment glooctl check is decently slower than glooctl check --exclude deployments,upstreams,rate-limit-configs,secrets,auth-configs So it would be nice if it worked.

[github-actions[bot]]

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.