Issue #3534: Tag compute resources according to the tool's metadata

The current PR provides implementation for issue #3534

The following changes were added:

a new preferences cluster.instances.tags. This preference supports tool/run_id/owner keys only.
```
{
"owner": "CP_OWNER",
"run_id": "CP_RUN_ID",
"tool": "CP_TOOL"
}
```
a new preference cluster.instances.allowed.tags. This preferences allows to specify comma-separated list of string values. If tool's metadata key exactly matches the value from this list the corresponding metadata (a key-value pair) shall be added to compute resources tags. Name value is not allowed.
stop run behaviour modification: tags shall be removed from compute resources if run status changed to final.
attach disks: tags shall be added to a new disks.
nodeup and reassign_node scripts support new --tags option. This option accepts a list of = string values. If this list provided the corresponding tags shall be added to instances and ebs volumes.
if CP_CAP_SHARE_FS_TYPE=lustre corresponding tags shall be added to created FS.

NOTE: all changes implemented for AWS provider only.

epam / cloud-pipeline