chore(deps): update dependency @eslint/eslintrc to v3.3.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
@eslint/eslintrc	devDependencies	patch	3.3.0 -> 3.3.1

---

Release Notes

eslint/eslintrc (@​eslint/eslintrc)

v3.3.1

Compare Source

Bug Fixes

• correct types field in package.json (#​184) (2f4cf3f)

---

Configuration

📅 Schedule: Branch creation - "* 0-4,22-23 * * 1-5,* * * * 0,6" (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 was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Update the @eslint/eslintrc devDependency to version 3.3.1 to incorporate a bug fix related to the 'types' field in package.json.

Bug Fixes:

• Update @eslint/eslintrc to v3.3.1 to correct the 'types' field in package.json.

Chores:

• Update devDependency @eslint/eslintrc from version 3.3.0 to 3.3.1.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the @eslint/eslintrc package from version 3.3.0 to 3.3.1 in the package.json file, addressing a bug fix related to the 'types' field in the package.json of the @eslint/eslintrc package.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update @eslint/eslintrc dependency to version 3.3.1.	Updated the version of @eslint/eslintrc from 3.3.0 to 3.3.1 in the package.json file. This update includes a bug fix for the 'types' field in the package.json of the @eslint/eslintrc package.	kit/dapp/package.json

Possibly linked issues

• chore(deps): pin dependencies #1: The PR updates @eslint/eslintrc, which is listed in the issue's dependency updates.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.