Extended dry-run for all procedures

[ilia1243]

Consider implementing new dry-run or replace existing --without-act.

• Do not change anything on cluster or in input Kubemarine files.
• Generate, enrich, compile as much as possible
  • Compile plugin templates
  • dry-run helm if it is supported
  • Enrich default plugins
  • Generate different files in dump (etc_hosts, haproxy configs, etc.) without upload.
  • Generate final inventory file without replacing of initial (as --without-act currently does)
  • Other
• Consider restrictions when generation of something that depends on real work on cluster (for example, template plugins sometimes depend on shell command through runtime_vars).
• In case if it is implemented only locally, consider adding this to kubemarine selftest.

[Deo121996]

Approach:
For implementing the dry-run we are setting the dry-run field in a cluster context. actual calls for the write function will be received at the wrapper function to prevent actual executions on nodes for sudo/run/put(etc) functions that are making actual changes to the nodes. So whenever the Kubemarine procedure calls to run sudo/run/put it just prints a debug log and all the functionality works similarly except uploading files to the nodes or executing commands on the nodes.

Status:
Currently completed dry-run implementation for install, upgrade, add_node, and reboot procedure. Working on remaining procedures to support dry-run.