[EPIC] - Consolidation of local environments

[IvoGoman]

Priority

(Medium) I'm annoyed but I'll live

Description

Currently there are three mechanism to spin up Greenhouse locally:

• dev-env
  • docker compose based setup that runs Operators and UI locally
  • bootstrapping of Greenhouse resources possible
  • no automatic onboarding of clusters
• e2e framework
  • allows spinning up KinD clusters and run the Operators
  • onboarding of clusters is possible within tests
  • not easily accessible outside of tests
• localenv
  • CLI-based tool that provides the ability to spin up Greenhouse in a KinD cluster
  • no bootstrapping of Greenhouse resources (yet)
  • no automatic onboarding of cluster (yet)
  • no access to the Dashboard (yet)
  • could be used from the tests

Acceptance Criteria:

• [FEAT] - localenv spins up a Greenhouse Dashboard #687
• [FEAT] - E2E Workflow #467
• [FEAT] - One command for running localenv environment #685
• [FEAT] - Update Contribution Guide for Local Dev setup #686
• Consolidation of the three toolings into the localenv
• [FEAT] Enable local Plugin Helm Chart development with the dev-env #736

Reference Issues

No response