Feat/add multimaster e2e tests

[KraMorK]

Description

Why do we need it, and what problem does it solve?

Why do we need it in the patch release (if we do)?

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: <kebab-case of a module name> | <1st level dir in the repo>
type: fix | feature | chore
summary: <ONE-LINE of what effectively changes for a user>
impact: <what to expect for users, possibly MULTI-LINE>, required if impact_level is high ↓
impact_level: default | high | low

[KraMorK]

/e2e/run/aws
/e2e/use/multimaster

[deckhouse-BOaTswain]

🔴 e2e: AWS for deckhouse:feat/add-multimaster-e2e-tests failed in 52s.

Workflow details (1 job failed)

🔴 e2e: AWS, Containerd, Kubernetes 1.27 failed in 12s.

[deckhouse-BOaTswain]

🔴 e2e: AWS for deckhouse:feat/add-multimaster-e2e-tests failed in 2m53s.

E2e for aws WithoutNAT;containerd;1.27 was failed. Use:

/e2e/abort aws;WithoutNAT;containerd;1.27 10880609933 10880609933-1-con-1-27 /sys/deckhouse-oss/install:pr333-test-1 - for abort failed cluster

Workflow details (1 job failed)

🔴 e2e: AWS, Containerd, Kubernetes 1.27 failed in 2m6s.

[KraMorK]

/e2e/abort aws;WithoutNAT;containerd;1.27 10880609933 10880609933-1-con-1-27 /sys/deckhouse-oss/install:pr333-test-1

[deckhouse-BOaTswain]

🟢 destroy cluster: AWS for refs/heads/main succeeded in 40s.

Workflow details

🟢 destroy cluster: AWS, Containerd, Kubernetes 1.27 succeeded in 15s.