refactor: update eslint and configs

[mfranzke]

Proposed changes

#4780 fails because of inconsistent eslint versions. Additionally removed an obsolete dependabot config that prevented major eslint update PRs, which got introduced with commit 2700279, but as we even already have eslint updated in package.json this should be obsolete, but prevented the update in showcases/patternhub/package.json.

Types of changes

• Bugfix (non-breaking change that fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improvements to existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

[github-actions]

🔭🐙🐈 Test this branch here: https://db-ux-design-system.github.io/core-web/review/refactor-update-eslint-and-configs

[Copilot]

Pull Request Overview

This PR addresses version inconsistencies in ESLint configuration by updating ESLint versions across the project and removing an obsolete Dependabot configuration that was preventing major ESLint updates.

• Updated ESLint from different versions (8.57.1 and 9.29.0) to a consistent 9.33.0 across all packages
• Updated ESLint configuration packages to compatible versions
• Removed Dependabot ignore rule for ESLint major version updates

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
showcases/patternhub/package.json	Updated ESLint from 8.57.1 to 9.33.0 and eslint-config-next to 15.5.0
package.json	Updated ESLint from 9.29.0 to 9.33.0 and eslint-config-xo to 0.49.0
.github/dependabot.yml	Removed obsolete ESLint major version update ignore rule

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 079ccea

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