Description

• Related to OU-1023, monitoring-plugin PR, perses-plugins PR
• Goal: Perses/perses needs to import the new releases in perses-plugin that contains this PR, which allows `__mf/js/async' files to use a proxy path to deliver JavaScript assets.
• Reason/Context: Without this change, the JavaScript assets use the default path `plugin/<PluginName>` rather than `<Proxy>/plugin/<PluginName>`, for example, `http://localhost:9000/api/proxy/plugin/monitoring-console-plugin/perses/plugins/Tempo/__mf/js/async/8597.d5ba4ca7.js`

• Steps: 
  •  upstream >> perses/plugins
    • Create a new release that contains this PR
  •  upstream >> perses/perses
    • 1. Update plugin versions based on new release in perses/plugins  https://github.com/perses/perses/blob/main/scripts/plugin/plugin.yaml
    • 2. Create release 
  • ? (Double Check this) upstream >> rhobs/observability-operator 
    • Create Perses image from new release and push to: quay.io/openshift-observability-ui/perses:v0.52.0-go-1.23
    • Update /observability-operator/cmd/operator/main.go 
      • `var defaultImages = map[string]string {  ...  "perses": "quay.io/openshift-observability-ui/perses:v0.52.0-go-1.23",   }`
      • Then Perses CR will be created here with new perses image containing our changes https://github.com/rhobs/observability-operator/blob/aadd6167e6445b2c50f4cf6a83003d3987350104/pkg/controllers/uiplugin/monitoring.go#L324

Goal

In monitoring-plugin >> perses dashboards, module federation can fetch JavaScript assets from the deployed perses instance using the reverse proxy `api/plugin/monitoring-console-plugin/proxy/__mf/js/async/plugins/<pluginName>/<assetHash>.js`