feat:support tailwindcss v4

[SisyphusZheng]

update /www and tailwind-plugin to support tailwind v4.

Thanks to the merge of #3034, the work of integrating and advancing #2903 is promoted.

related #3034
related #2903

close #3056
close #2819

--patch-1
based on review,

1. del compiler and make it more clean and simple,
2. fix init tailwind part,
3. fix test tailwind part

--patch-2

1. fix the docs
2. fix the docs of plugin and version

--patch-3

1. Addressed various maintenance tasks (chores)
2. Updated the Tailwind CSS plugin to align with this release. Generated a fresh project using the updated init configuration and
3. deployed it via Deno Deploy EA. Deployment is functioning correctly.

--patch-4
Move postcss imports to Tailwind section in init script

--patch-5
Refactored Tailwind plugin type definitions by copying PluginOptions properties from @tailwindcss/postcss and adding Fresh-specific exclude option, while exporting types from package entrypoint for better accessibility.

Test Project: https://fresh.fresh-press.deno.net/
Test Project Repository: https://github.com/SisyphusZheng/fresh-tailwindv4
Test Plugin: https://jsr.io/@freshpress/fresh-plugin-tailwind@1.0.0

[iuioiua]

Instances of tailwind() not being awaited still remain in the codebase. E.g. https://github.com/SisyphusZheng/fresh/blob/aac6207306cfcda2405e2761958136fb637cf470/docs/canary/examples/migration-guide.md?plain=1#L62. I suggest searching for "tailwind(".

[SisyphusZheng]

Instances of tailwind() not being awaited still remain in the codebase. E.g. https://github.com/SisyphusZheng/fresh/blob/aac6207306cfcda2405e2761958136fb637cf470/docs/canary/examples/migration-guide.md?plain=1#L62. I suggest searching for "tailwind(".

thx for pointing out this issue. This is actually part of the documentation and does not affect the code. I hope the documentation can be revised later.

Of course, I will also double-check if there is any code that hasn't been actually fixed.

[iuioiua]

But it matters that the documentation is correct according to the implementation. Otherwise, users will be mislead on how to use tailwind().

[SisyphusZheng]

But it matters that the documentation is correct according to the implementation. Otherwise, users will be mislead on how to use tailwind().

I understand the importance of this issue now and will make the modification. Thank you.

[iuioiua]

LGTM!

[iuioiua]

Is --allow-scripts required now? Genuine question. I haven't checked. If so, we should consider whether other tasks such as build need it too, including those created from the init script.

[SisyphusZheng]

The oxide script requires --allow-script during deno install, and I can't figure out a way to avoid this warning for the time being.

[iuioiua]

Are you able to resolve the merge conflicts? @marvinhagemeister, are you able to take a look? It seems a lot of people would love to have this added.

[marvinhagemeister]

Resolved the merge conflicts, but it looks like the PR is not yet ready to be merged. Several aspects of the site in www are missing styling and look broken. I've followed the update instructions on this page https://tailwindcss.com/docs/upgrade-guide and applied them, but looks like there is more going on.

main:

This PR:

[marvinhagemeister]

LGTM, Thanks for updating the plugin! I've went ahead and updated the code in www for v4 too.