Create `kpops init` command

Description

Command: init

Generates an empty KPOps pipeline project with flat file structure.

Flags:

--path: Path where project is to be initiated. str default: '.' (Optional)
--name: Name of the project's root folder. Could be omitted and included in path. str, default: 'None'
--schema: Path to a schema to use for generating one of the .yaml files. Related file inferred from the schema name. Can contain the paths to up to 3 schemas, 1 for each generated file. Use the ones online by default. str[], default: None (Optional)
--detailed: Whether to generate the files with every single option for every component or only the required fields, per the schema. bool, default: true (Optional)
--components: The names and types for all components to be included in the generated files. str[], default: 1 of each component, named after the component type. (Optional)
--config-preset: Choose preset for the config. A couple available. If a preset with more than 1 env ( A list of commented environments as suggestions? ) is chosen, the corresponding specific{env}_defaults.yaml are generated. str, default: "empty" (Optional)
--defaults-preset: Choose preset for the defaults. A couple available. str, default: "empty" (Optional)
--kpops-version: KPOps with which the project would be used. More of a distant feature idea. Took it from the examples. A "Could have" at most. str, default: "latest" (Optional)