Chore/package bumps tailwindcss to v4

[rubentalstra]

Summary

This pull request includes updates to dependencies, configuration files, and several UI components to improve code consistency and functionality. The most important changes include updating dependencies in package.json, modifying configuration files, and adjusting class names for better styling.

Dependency Updates:

• client/package.json: Updated multiple dependencies including tailwind-merge, tailwindcss, @vitejs/plugin-react, and more. [1] [2] [3] [4] [5]

Configuration Changes:

• .prettierrc: Changed tailwindConfig file extension from .cjs to .mjs.
• client/postcss.config.cjs: Removed the file entirely.

UI Component Adjustments:

• client/src/App.jsx: Modified RadixToast.Viewport class name for consistency.
• client/src/components/Artifacts/ArtifactTabs.tsx: Changed className from flex-grow to grow for better styling. [1] [2]
• client/src/components/Artifacts/Code.tsx: Adjusted whitespace-pre class for better code formatting.
• client/src/components/Audio/Voices.tsx: Updated sizeClasses to ensure proper max-width styling. [1] [2] [3]
• client/src/components/Auth/*: Various changes to improve styling and focus behavior, including focus:outline-hidden and class name adjustments. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]

Change Type

Please delete any irrelevant options.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Translation update

Testing

Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.

Test Configuration:

Checklist

Please delete any irrelevant options.

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes
• Any changes dependent on mine have been merged and published in downstream modules.
• A pull request for updating the documentation has been submitted.

[rubentalstra]

Was just an idea. Breaking changes for tailwindcss going from v3 to v4. Currently not in scope was a test.