refactor(core): Refactor the Virtualization Controller configuration

[yaroslavborbat]

Description

This PR refactors the Virtualization Controller configuration by consolidating disparate settings previously scattered across flags and environment variables into a unified configuration object:

apiVersion: configuration.virtualization.deckhouse.io/v1alpha1
kind: VirtualizationControllerConfiguration

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: core
type: chore
summary: Refactor the Virtualization Controller configuration 
impact_level: low

[Isteb4k]

1. Why do we need a cobra? Increases cognitive complexity.
2. Why are some parameters stored in a config map, others passed through envs, and the third are passed as arguments?
3. The controllers map is difficult to read, it is unclear what we gain by starting to use it. When constructors were called sequentially, the code was more sparse and perceived more orderly

[ldmonster]

Suggested change

	x-examples: ["sc-1", "sc-2"]
	x-dmt-default: ["sc-1", "sc-2"]
	x-dmt-default: ["sc-1", "sc-2"]
	x-doc-examples:
	- ["sc-1", "sc-2"]