Release Lock Management v2

[ilya-lesikov]

Before proceeding

• I didn't find a similar issue

Problem

There are numerous problems in how werf handles locking during deployment phase. Some issues were solved in v2, but not all.

Solution (if you have one)

Release locking should be performed against the release namespace instead of the ConfigMap "werf-synchronization" in the release namespace. This way we can safely lock all operations on the release namespace itself, such as adding labels or annotations to it or removing namespace in werf dismiss.

Additional information

Refs: #97, #85