Consistent werf-converge and werf-dismiss process locking

[distorhead]

Werf-converge and werf-dismiss commands lock release by name. Lock is stored in the kubernetes namespace.

When --with-namespace option has been specified werf-dismiss command does not use release lock at all for now.

Werf-dismiss command should:

• lock release while deleting helm release;
• unlock release;
• delete kubernetes namespace when --with-namespace option has been specified;
• do not wait until kubernetes namespace deleted, exit immediately.

Werf-converge command should:

• await until kubernetes namespace deleted if namespace is being deleted at the moment;
• lock release;
• perform release install/upgrade;
• unlock release.

[distorhead]

The following scenario should be taken into account:

• werf-dismiss command deleted helm release and unlocked a release;
• werf-converge acquired a lock and already started creating new release;
• werf-dismiss command starts deleting kubernetes namespace; => FAIL

[ilya-lesikov]

The only way to consistently lock not only release operations but also release namespace operations is locking both the release namespace and release by locking the release namespace, instead of locking "werf-synchronization" ConfigMap