Move Kyma-dashboard to busola

[dbadura]

Description
Prepare simplification to improve release process for busola by unification of kyma-dashboard repository with busola.

Reasons

• One release instead of two
• One busola-web image with different configuration instead of 4 images in total
• Bugs for kyma-dashboard can be catched at busola development instead when bumping busola in kyma-dashboard

Execution

• Add ability to configure different path for configuration - Configure busola to use different configuration #3299
• Add dockerfile to build busola with all configuration inside. Proposal: create kymadirectory in busola - feat: Add Kyma config from kyma-dashboard #3321, feat: Unify nodejs version for building #3332
• Add github actions to build new image type
• Add integration tests from kyma-dashboard - feat: Add integration test from kyma-dashboard #3333
• Allow adjusting environment in busola k8s kustomize - feat: Add overlays with environments configuration #3344
• Adjust environments to pickup correct environment
• Add documentation feat: Update docs about recent changes related to kyma-dashboard #3347, docs: Update docs about busola-kyma image #3402
• Add test to check k8s configuration covered by smoke tests
• Cleanup old unneeded files chore: Unify dockerfiles #3404

Cleanups and known issues

• When there is no yaml for specific resource, busola by default serves js and consume it. Which results in high cpu usage and many warnings, errors in console. fix: infinite loop on hidden namespace #3373
• Unify cypress commands in tests chore: Merge kyma tests into integration #3388, docs: Update docs merge tests #3407
  Attachments

[dbadura]

Known issues:

• When there is no yaml for specific resource, busola by default serves js and consume it. Which results in high cpu usage and many warnings, errors in console.

Cleanups:

• Unify cypress commands in tests

[dbadura]

Sync of Kyma Dashboard: #3352