Improve Performance of many helm chart based pages

[richard-cox]

Summary

Fixes #10448

Occurred changes and/or fixed issues

• Reverts This fixes an issue where catalog/charts were stale after a repo was updated #7672, which was the fix for Chart Repository refresh does not actually refresh the chart repo #7668. Supersedes another fix Change the way we get up to date catalog information to be more performant #10733
• This fixes an issue where catalog/charts were stale after a repo was updated #7672 revolved around a very outlier case where there was an update to an existing chart version (which are normally immutable) and using the 'Refresh' helm repo action failed to update it (note refreshing browser was a workaround)
• The fix for This fixes an issue where catalog/charts were stale after a repo was updated #7672 brought in a costly refresh of each helm repo at many different points in the dashboard. This impacts performance as users navigate around the dashboard, but we've also had customer's with large repos reporting timeouts which was compounded by that change. Change the way we get up to date catalog information to be more performant #10733 improved this by instead not caching individual chart versions and always going out and fetching them.
• See comment Change the way we get up to date catalog information to be more performant #10733 (comment) why this isn't so great
• This PR contains an improvement where we clear the version cache whenever we clear the chart cache

Technical notes summary

• setting reset when calling catalog/load cleared the existing chart cache. This is called in four places
  • repo model's refresh action - force + reset
  • cluster tools visit - force + reset (not sure why we need to do this)
  • plugins page visit - reset
  • plugins page refresh button - reset + force
• now reset also clears the chart version cache

Areas or cases that should be tested

• Refreshing helm repos
• Cluster tools page
• Extensions page

Areas which could experience regressions

Areas as above

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