chore(deps): bump the dependencies group across 1 directory with 35 updates

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sentry]

Bug: The Tailwind CSS upgrade to v4 is incomplete. The configuration uses deprecated @tailwind directives and the code contains legacy utility classes that will silently fail, causing visual regressions.
_{Severity: CRITICAL}

Suggested Fix

Update the CSS entry file to use @import "tailwindcss";. Migrate the tailwind.config.js to the new CSS-first configuration format. Replace all legacy utility classes (e.g., bg-gradient-to-*, flex-shrink-0) with their v4 equivalents (e.g., bg-gradient-*, shrink-0). Consider adding a build step to the CI pipeline to catch such issues in the future.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L156

Potential issue: The application's CSS configuration is incompatible with the upgraded
Tailwind CSS version (`^4.2.1`). The code still uses the old `@tailwind` directives,
which are no longer supported. Additionally, the codebase contains legacy utility
classes like `bg-gradient-to-*` and `flex-shrink-0` which were removed in Tailwind v4.1+
and will no longer generate styles. Since the CI process lacks a build step, these
styling issues will not be caught before deployment, leading to visual regressions and
broken layouts in the production application.

_{Did we get this right? 👍 / 👎 to inform future reviews.}