Scope reconciler

[tmilos77]

Description

Changes proposed in this pull request:

• removed on-first-use Scope creation and created dedicated Scope reconciler that's watching Kyma CR
  • added Scope KCP reconciler by moving most of the components/kcp/pkg/common/actions/scope actions into components/kcp/pkg/kcp/scope
  • it is responsible for the provisioning once CloudManager module is ready in the Kyma CR status
  • it handles
    • Kyma CR finalizer
    • Scope creation with finalizer
    • adding SKR to the Looper
• refactored cloudcontrolv1beta1 resources
  • made ScopeRef required
  • removed KymaName since it should be read from the Scope
• removed Kyma watch from KCP NfsInstance reconciler, since it's added to the new Scope reconciler
• refactored focal flow to set error condition and stop/forget if referred Scope does not exist
• refactored focal.CommonObject and removed KymaName() since it's removed from the resources, and embedded composed.ObjWithConditions as a replacement for Conditions() and GetObjectMeta()
• removed deleted components/kcp/pkg/common/actions/scope flow from all existing reconcilers
• changed SKR IpRange reconciler in components/kcp/pkg/skr/iprange to create KCP IpRange w/out deleted KymaName and with required ScopeRef
• extracted skrlooper.ActiveSkrCollection interface from skrlooper.SkrLooper with AddKymaName() and RemoveKymaName() methods, to be provided to the flow actions to start/stop SKR reconciliations, w/out giving them reference to the whole SkrLooper
• added func util.GetKymaModuleState(), type util.KymaModuleState, and related consts to match LifecycleManager implementation
• added func SetObj() to the composed.State due to a non-standard Scope flow when it's triggered by the watched Kyma in case when Scope does not exist, so it can be set to the state once created
• fixed a WaitGroup bug Amir discovered about order and place of Add() calls

Related issue(s)

[ravi-shankar-sap]

lgtm