chore(deps): update dependency eslint-config-standard-with-typescript to v43

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-standard-with-typescript	^39.0.0 -> ^43.0.0

---

Release Notes

standard/eslint-config-standard-with-typescript (eslint-config-standard-with-typescript)

v43.0.0

Compare Source

⚠ BREAKING CHANGES

• add rule @​typescript-eslint/prefer-return-this-type

Features

• @​typescript-eslint/prefer-return-this-type (d987ba3)

v42.0.0

Compare Source

⚠ BREAKING CHANGES

• add rule @​typescript-eslint/no-unsafe-argument

Features

• @​typescript-eslint/no-unsafe-argument (350bd29)

v41.0.0

Compare Source

⚠ BREAKING CHANGES

• add rule @​typescript-eslint/non-nullable-type-assertion-style

Co-authored-by: Rostislav Simonik [email protected]

Features

• @​typescript-eslint/non-nullable-type-assertion-style (3f94c58)

v40.0.0

Compare Source

⚠ BREAKING CHANGES

• add rule @​typescript-eslint/unbound-method

Features

• @​typescript-eslint/unbound-method (2ec6d24), closes #​1327

v39.1.1

Compare Source

Build system / dependencies

• renovate shared config (e83cfd8)
• unpin actions (18c0988)

Bug fixes

• turn off ESLint no-implied-eval (ed8f1d4)

v39.1.0

Compare Source

Build system / dependencies

• add-to-project workflow (dd3ceae)
• automergeMinor eslint-config-standard (f531394)
• tsconfig.module = nodenext (7590972)

Features

• docs: replace npm@<7 with yarn (4dbc4b7), closes #​1254

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.
Backend
Frontend

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow