[FEAT] - 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:

• Consolidation of the three toolings into the localenv
• e2e tests use the localenv to spin up the test environment
• localenv supports one command to
  • spin up Greenhouse Operator in a KinD Cluster
  • bootstrap demo resources e.g. here, but at least a Demo Organisation
  • Onboarding of a single Cluster into the Demo Organisation
  • Spin up the Greenhouse Dashboard running against Greenhouse in the KinD cluster
    • Access from Dashboard to KinD API Server via Token??
• Updates to the Documentation Page
• Bonus: Enable the same Plugin development flow as with the dev-env

Reference Issues

No response