chore(deps): update dependency concurrently to ^4.1.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
concurrently	^4.1.1 -> ^4.1.2

---

Release Notes

open-cli-tools/concurrently (concurrently)

v4.1.2

Compare Source

• Don't strip quotes if they are impaired (#​118, #​194)

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

error Couldn't find match for "feat/resolve_dts" in "refs/heads/deprecation,refs/heads/master,refs/pull/1/head,refs/pull/10/head,refs/pull/11/head,refs/pull/13/head,refs/pull/2/head,refs/pull/3/head,refs/pull/4/head,refs/pull/5/head,refs/pull/6/head,refs/pull/7/head,refs/pull/8/head,refs/pull/9/head,refs/tags/v0.2.0,refs/tags/v0.3.0,refs/tags/v0.4.0,refs/tags/v0.4.1,refs/tags/v0.4.2,refs/tags/v0.5.0,refs/tags/v1.0.0,refs/tags/v1.0.1,refs/tags/v1.0.2,refs/tags/v1.1.0,refs/tags/v1.1.0-rc.1,refs/tags/v1.1.1" for "https://github.com/JounQin/eslint-import-resolver-typescript.git".

[changeset-bot]

⚠️ No Changeset found

Latest commit: 34e2fc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR