Remove config layer

[ruanxin]

Since now we only support raw manifest rendering, the config layer which was previously provided as helm chart, kustomize overwrite becomes useless. We should remove any config.yaml related code in lifecycle manager.

AC:

• CLI don't need to handle config.yaml, and generated module template should not contains config layer.
• Drop the code from the CLI related to the config layer
• For module template which contains config, the config layer will not rendered into manifest CR.
• All code in lifecycle manager related handling this config should be removed
• Update the description in the ModuleTemplate CRD to indicate that the config field is no longer used

Be aware, eventually, manifest spec should not contain this config field, but this might introduce breaking changes, should plan it in next API version. In this issue, don't remove this Config field.

type ManifestSpec struct {
	// Config specifies OCI image configuration for Manifest
	Config ImageSpec `json:"config,omitempty"`

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[janmedrek]

The CLI part is already done with the new way of building the Modules (based on the config file and not the kubebuilder repo).

[LeelaChacha]

One PR is still left