[2.9] Use BundleDeployment status to calculate GitRepo resources

[aruiz14]

Summary

Fixes #12517

Occurred changes and/or fixed issues

GitRepo details include a tab for Resources, which iterates over the list of status.resources in the GitRepo object. However, this is inaccurate, since the source of truth for resources are BundleDeployments, as they may vary depending on the target cluster customization.

Technical notes summary

• The code used find to pick just the first bundle deployment matching the cluster label, which is totally wrong. Now we iterate directly on bundle deployments instead, then pick the target cluster as necessary.
• The biggest part of the Bundles payload is the spec.resources, as it basically contains all the raw chart contents. I've modified the getter to make steve omit that field.
  • In order to allow this, I also had to refactor the Bundle view to not use the spec for listing resources (and use the status instead).

Areas or cases that should be tested

• Continuous Delivery: GitRepos
• Continuous Delivery: Advanced > Bundles

Areas which could experience regressions

This PR actually aims to provide the same output while changing how the information is computed.

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[moio]

LGTM as a first glance.

Not sure if applicable unit tests exist?

[moio]

Also: linter failing.

[richard-cox]

haven't done much functional testing. once we work through some of the code review items will crack on

[richard-cox]

I'm looking into the bug that fails to show the correct resource state (reopened comment)

[richard-cox]

Looks good now. Just blocked on branch opening up to 2.9.5 changes (and e2e tests passing)