Automatically update Support Bundle during run

[chris-sanders]

Problem statement

If we implement atomic mergable CRD based support bundles as requested in #651 we should then be able to include as part of the collection process a check for newer versions of the spec.

This would allow a spec to be updated separately from the application. It follows that a new version of a product would have new issues that are not known before the release of the product. This allows the spec to be updated during the life of the application version for the inevitable new learnings in the field without requiring the user to upgrade the application.

Proposal

Add fields to the Mergable Support Bundle CRD to track the version and upstream URL for a SupportBundle. When collecting check the URL for a newer version and if available install the newer bundle in the cluster and use it for the collection.

As with anything 'automatic' there should be a way in troubleshoot to disable any form of updates although the default experience should be to try and update.

Additional considerations

It should be verified or included that troubleshoot should work with proxies if it doesn't today.

Out of scope

Troubleshoot need not deal with air-gap environments that can not reach the listed upstream URL. Other tooling can be used to update or redirect that field if troubleshoot is intended to update in these type of environments from an alternate URL. Although troubleshoot should fail gracefully and still do the collection without an extreme delay due to possibly multiple timeouts.