build: update dependency eslint-config-prettier to v10

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
eslint-config-prettier	devDependencies	major	9.1.0 -> 10.0.1

---

Release Notes

prettier/eslint-config-prettier (eslint-config-prettier)

v10.0.1

Compare Source

eslint-config-prettier

10.0.1

What's Changed

• chore: migrate to changeset for automatically releasing by @​JounQin in https://github.com/prettier/eslint-config-prettier/pull/278
• add support for @stylistic/eslint-plugin by @​abrahamguo in https://github.com/prettier/eslint-config-prettier/pull/272

New Contributors

• @​JounQin made their first contribution in https://github.com/prettier/eslint-config-prettier/pull/278
• @​abrahamguo made their first contribution in https://github.com/prettier/eslint-config-prettier/pull/272

Full Changelog: prettier/eslint-config-prettier@v9.1.0...v10.0.1

v10.0.0

Compare Source

Major Changes

• #​272 5be64be Thanks @​abrahamguo! - add support for @​stylistic formatting rules

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 Renovate Bot.

[angular-robot]

⚠️ 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: pnpm-lock.yaml

/bin/sh: 1: pnpm: not found

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}