fix(tailwind): className manipulation for component props

[gabrielmfern]

This is meant so that it allows users to use twMerge with respective
components without it having any issues.

For background, we inline all styles from Tailwind classes and then remove the
classes. This is done on the props of all React elements inside of the Tailwind
component's children. This means that classNames are removed before the user
can deal with them to merge or manipulate in general.

The reason we can't just direclty not run Tailwind on the components and just
leave the classNames be, is because our components specifically do manipulation
on the styles. Meaning that, if only the classNames come in to be manipulated,
the components won't do what they would normally do.

The way this PR goes around that issue is then, by still running Tailwind on
the component, thus adding the proper style properties to the component, but
without removing the respective classNames. This still allows us to do style
manipulation while allowing users to do className manipulation in the same way.

There is still one issue that might arise from this, though. When using the
<Button> component, for example, we do some transformations to the padding
before actually applying it to the underlying <a> element while still adding
the needed classNames to the same element. Since, the current behavior of the
component is to give priority to the new styles from Tailwind classNames over
the already inlined styles, it means that these transformations will be ignored
in our component making it not work the same way as before. The only to fix
this, is to do the opposite of what we already do — we need to give priority to
the already inlined styles on elements.

This last change is still a trade-off though, and might be a bit unintuitive to
users. So, something to lookout for.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9302024

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@react-email/tailwind	Minor
@react-email/components	Patch
react-email-starter	Patch
create-email	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-email	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 31, 2024 5:30pm
react-email-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 31, 2024 5:30pm