Bump up RHDH to 1.9 and RHDH chart to 5.0.2

[thepetk]

What does this PR do?

The PR bumps up the RHDH version to 1.9 and the RHDH Chart version to 5.0.2:

• Version 5.0.2 has been selected looking at the rhdh-chart chart.yaml for release-1.9 branch.
• A refinement (also grouping) of all plugins has been done.
• We have removed the plugin suffix as it's no longer required. For example the oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-lightspeed-backend:bs_1.45.3__1.1.1!red-hat-developer-hub-backstage-plugin-lightspeed-backend is now oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-lightspeed-backend:bs_1.45.3__1.1.1
• In 5.0.2 the nameOverride for the backstage deployment is changed to developer-hub. In order to keep the same deployment resource I'm keeping the basktage one. This will just rollout a new update of the existing deployment on openshift -> instead of replacing with a new one.
• A tmp volume has been created as the scaffolder actions where complaining upon testing

Which issue(s) does this PR fix

Fixes RHIDP-11152 & RHDHBUGS-2502

How to test changes / Special notes to the reviewer

I have tested the suggested changes on a test cluster of mine thoroughly:

• Lightspeed works as expected
• Software templates can be deployed and tekton pipelines work fine
• Header and Homepage are aligned with the vanilla one. The only change is on the application-launcher dropdown

I have also tested the exact deployment scenario -> meaning I have created an instance on RHDH 1.8 with RHDH Chart 3.1.1 and then went up to RHDH 1.9 & RHDH-chart 5.0.2

The changes in the plugins are based on:

• https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.9/modules/dynamic-plugins/rhdh-supported-plugins.csv
• https://github.com/josephca/red-hat-developers-documentation-rhdh/blob/ec4edc7eac25efe896182615eebbc47914bb37fc/modules/dynamic-plugins/ref-community-plugins-migration.adoc

[thepetk]

Replaces #77

[thepetk]

Sharing here screenshots from the tests:

• OCP Deployment successful:

• Global header and Homepage aligned to vanilla except the custom dropdown

• Using RHDH 1.9 and Backstage version 1.45.3

• Created software template app and pipelines work as expected:

• Lightpseed works as expected

[gabemontero]

any chance of pointing your test env to the dev cluster's RHOAI endpoints and seeing if the model catalog bridge / openshift ai connector works @thepetk ?

[thepetk]

any chance of pointing your test env to the dev cluster's RHOAI endpoints and seeing if the model catalog bridge / openshift ai connector works

@gabemontero I've tried something different without pointing the connector to the devCluster:

• Verified my Openshift AI Operator is at the same version with the one we currently have on devCluster (2.25.1)
• Registered a new model through RHOAI
• I'm able to see this model registered in RHDH
• Logs from the model catalog pods look OK.

Happy to perform the test you're suggesting, for sure I'll need a bit more time to make it happen. Just in case let me know if my test above covers your concerns

[gabemontero]

any chance of pointing your test env to the dev cluster's RHOAI endpoints and seeing if the model catalog bridge / openshift ai connector works

@gabemontero I've tried something different without pointing the connector to the devCluster:

• Verified my Openshift AI Operator is at the same version with the one we currently have on devCluster (2.25.1)
• Registered a new model through RHOAI
• I'm able to see this model registered in RHDH
• Logs from the model catalog pods look OK.

Happy to perform the test you're suggesting, for sure I'll need a bit more time to make it happen. Just in case let me know if my test above covers your concerns

that test is totally a viable alternative @thepetk .... simply tried to convey the "simplest" option when putting forth that option

[gabemontero]

by no means wanted to gate the review of this on the comment, but I wonder @thepetk @johnmcollier if we should push a copy of quay.io/tpetkos/customized-sign-in-page:v0.1.0 to quay.io/redhat-ai-dev

wdyt?

[johnmcollier]

Yeah, let's push it under redhat-ai-dev

[johnmcollier]

Changes look good

@thepetk Can you confirm if the Tool calling/trail UI shows up with the updated Lightspeed?