Remove tailwind_merge from generator

[stephannv]

Removing bundle add tailwind_merge from install command since tailwind_merge is already a dependency from rbui.

[cirdes]

@stephannv, there's a catch to that.

We want RbUI to also be used with the gem added only in the development environment. The gem would function like the ShadCn CLI, allowing us to generate or eject the components we need, as needed.

Maybe we should adjust the generator to only add tailwind_merge in that scenario.

Going even further, that should be the recommended way of using the gem.

What are your thoughts, @SethHorsley?

[stephannv]

Nice. I think is a nice idea to allow devs to extract components to their apps, but IMO (as a new user), I would prefer to not handle all the needed boilerplate to achieve this (I ran rbui install and I got ~45 file changes and a bloated vendor/javascript folder). I would prefer all the freedom of customizing design/behavior of components but without the burden of handling low-level stuff, so I think a mix of two approaches would be great: rbui provides the base structure and we can extract things to our apps (like devise allowing to override controllers, views, callbacks, etc)

[SethHorsley]

@stephannv I agree. If you're using import maps that bloat in the vendor/js is needed for the gem to work properly right now. But it should not be doing that if you're not using import maps. I like the idea of when removing the gem you have to install tailwind merge manually.