fix: dependabot commit and tooling aligment

[carlosthe19916]

Summary

• Change dependabot title configuration to be aligned to the new commit message standards
• Remove biome and old references to libraries and align them to the new tooling

Summary by Sourcery

Align Dependabot configuration with new commit message conventions and updated tooling classifications.

Build:

• Update Dependabot commit message prefixes for GitHub Actions and npm updates to match new conventions.
• Retarget Dependabot linting and tooling dependency patterns from Biome and rsbuild to ESLint/Prettier and Vite/Vitest ecosystems.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update Dependabot commit message prefixes to match new commit standards and retarget dependency groups from old biome/rsbuild tooling to eslint/prettier and vite/vitest stacks.

Flow diagram for updated Dependabot commit prefixes and tooling groups

flowchart TD
  A[Dependabot update check] --> B{package-ecosystem}
  B -->|github-actions| C[Use commit-message prefix ci: ]
  B -->|npm| D[Use commit-message prefix chore deps: ]

  D --> E{dependency-group}
  E -->|linting-formatting| F[Match eslint and prettier patterns]
  E -->|tools| G[Match vite and vitest patterns]

Loading

File-Level Changes

Change	Details	Files
Align Dependabot commit message prefixes with new conventional commit standards.	Change CI-related dependency update prefix from an emoji-based ':ghost: ' to 'ci: ' Change npm dependency update prefix from ':ghost: ' to 'chore(deps): ' to match conventional commits	.github/dependabot.yml
Retarget Dependabot dependency grouping from biome/rsbuild to eslint/prettier and vite/vitest tooling.	Rename the 'linting' dependency group to 'linting-formatting' to better reflect coverage Replace biome-related patterns with eslint-related and prettier-related patterns for linting/formatting dependencies Replace rsbuild-related tooling patterns with vite- and vitest-related patterns while keeping @hey-api tooling	.github/dependabot.yml

---

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!

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]

Hey - I've left some high level feedback:

• If you want all formatter-related dependencies grouped, consider adding a prettier-* pattern alongside prettier under linting-formatting to catch plugins and related packages.
• Under tools.patterns, you might also include a vitest-* pattern in case you later add Vitest-related companion packages that don’t use the @vitest/* scope.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- If you want all formatter-related dependencies grouped, consider adding a `prettier-*` pattern alongside `prettier` under `linting-formatting` to catch plugins and related packages.
- Under `tools.patterns`, you might also include a `vitest-*` pattern in case you later add Vitest-related companion packages that don’t use the `@vitest/*` scope.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.68%. Comparing base (16a6bec) to head (68d9c7d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1073   +/-   ##
=======================================
  Coverage   50.68%   50.68%           
=======================================
  Files         253      253           
  Lines        5499     5499           
  Branches     1660     1660           
=======================================
  Hits         2787     2787           
  Misses       2440     2440           
  Partials      272      272           

Flag	Coverage Δ
e2e	68.93% <ø> (ø)
unit	2.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.