URI field that returns content that isn't a support bundle causes analysis to fail

[crdant]

Bug Description

I specified I URL to a non-existent object in Google Cloud storage, which led to an XML file being returned explaining the error. The caused the bundle analysis to fail when running kubectl support-bundle --load-cluster-specs.

Expected Behavior

The analyzers and collectors from the spec that is stored in the cluster will be run rather than the non-existent spec from the XML file leading to misbehavior.

Steps To Reproduce

You may be to reproduce with fewer steps, but this will make it most like what I encountered.

1. Include a uri field in a spec that points to a non-existent Google Cloud Storage object
2. Confirm a curl of that object returns an XML indicating an error
3. Store that spec in cluster with at least one other spec in the same namespace
4. Run kubectl support-bundle --load-cluster-specs
5. Observe that the TUI does not come up
6. Extract analysis.json from the bundle and notice its content is []