Task

See https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.9/html-single/interacting_with_red_hat_developer_lightspeed_for_red_hat_developer_hub/index#proc-installing-and-configuring-lightspeed_developer-lightspeed for more details on how Lightspeed can be integrated into RHDH.

Background

Dependencies and Blockers

QE impacted work
Documentation impacted work 

Acceptance Criteria

• It should expose an option similar to the `orchestrator.enabled` one to toggle the Lightspeed features (for example, `lightspeed.enabled`).
• Lightspeed features should be enabled by default in the configuration
• Similar to the Orchestrator, the list of plugins to enable when Lightspeed is enabled should be configurable in the values file. This is to help with disconnected environments
• Any adidtional configuration parameters for Lightspeed should be under the `lightspeed` scope in the values file.
• When Lightspeed is disabled, the additional sidecar containers should be removed from the resulting Deployment rendered by Helm
• It should ensure in-place upgrade CI checks pass in the Helm Chart
• It should add a values file in CI with Lightspeed disabled