fix: remove CSS compilation to prevent style conflicts

[dominik-warch]

Problem

The package was compiling and registering its own CSS file, which overwrites Filament's default styling. This is a common issue in Filament plugins that load compiled CSS files directly into the app.

Solution

Removed all CSS compilation infrastructure and migrated to Filament's recommended approach: users integrate the package's Tailwind classes into their custom theme.

Changes

• Removed CSS asset registration from FilamentCommentsServiceProvider
• Deleted resources/css/ and resources/dist/ directories
• Removed npm dependencies and build configuration (package.json, package-lock.json, yarn.lock, .prettierrc)
• Added installation instructions for integrating Tailwind classes via custom theme

Migration Guide

Users should add this to their custom theme's CSS file:

 @source '../../../../vendor/parallax/filament-comments/resources/**/*';

See the updated README for complete instructions.