Update .editorconfig

[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

[deckhouse-BOaTswain]

:red_circle: e2e: EKS for deckhouse:KraMorK-patch-3 failed in 34m35s.

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

/e2e/abort eks;WithoutNAT;containerd;1.27 11574355636 11574355636-2-con-1-27 /sys/deckhouse-oss/install:pr356-test-1 - for abort failed cluster

Workflow details (1 job failed)

:red_circle: `e2e: EKS` for `deckhouse:KraMorK-patch-3` [failed](https://github.com/deckhouse/deckhouse-test-1/actions/runs/11574355636) in 3m36s. E2e for eks WithoutNAT;containerd;1.27 was failed. Use: `/e2e/abort eks;WithoutNAT;containerd;1.27 11574355636 11574355636-1-con-1-27 /sys/deckhouse-oss/install:pr356-test-1 ` - for abort failed cluster

Workflow details (1 job failed)

:red_circle: `e2e: EKS, Containerd, Kubernetes 1.27` failed in 2m30s.

:fast_forward: `e2e: EKS, Containerd, Kubernetes 1.27` for `deckhouse:KraMorK-patch-3` [started](https://github.com/deckhouse/deckhouse-test-1/actions/runs/11574355636). :red_circle: `e2e: EKS, Containerd, Kubernetes 1.27` failed in 32s.