config: CNF Installation (3) Switch to new config usage

[kosstennbl]

Description

Adapt all usages of config to the new config v2 format.
Remove code that was used by old config, but serves no purpose with new config version.
Update all sample and example configs, use transformer if cnf_setup is called with non-latest version.

Issues:

Refs: #2135

[kosstennbl]

List of changes:

Most of changed *.cr files: adapt to new config (parsing, usage), won't be mentioned below.

• Workflow: use example from current commit, not main. (possibly could be moved out of PR)
• CNF_TESTSUITE_YML_USAGE.md: update docs for CNF config.
• embedded files: add config examples for different versions
• example/sample_cnfs: update to new format via config updater. Some manual modifications where was needed. Removal of some unused parameters.
• setup spec: removal of genereate_config tests as the process is now interactive. Add test for setup of v1 config.
• cnf_manager_spec: remove unneccessary tests.
• cnf_setup: replace generator, small naming changes
• constants: move rolling version tags outside of specific file. (Was planned to be used in config, redesigned later)
• setup: replace config validation task
• cnf_install/config: add updater to parsing, move and adapt some methods from old config
• install_common: remove functions which are not needed anymore
• cnf_manager: remove not needed functions, remove HelmDirectoryMissing exception (was used only as warning)
• config.cr, generate_config.cr: were deleted, fully replaced with v2 versions
• task: redone config generation for platform tests
• compatibility: move constant array to constants, removed validation (now in setup).
• state: redesign elastic_volumes test to not use Helm.kind_exists? (this Helm library method took testsuite config as argument. While writing this comment, i reminded myself of this, want to tear my hair once more)

[martin-mat]

lgtm