chore(deps): update `tailwindcss` to v4.*

[cstns]

Description

Upgrade Tailwind to latest version.

• bumping to 3.4.0 introduced some breaking changes
• so did bumping to 4.*

After addressing the breaking changes, I did a quick comparison between production and local, and nothing major appeared to have changed.

Related Issue(s)

TBD

Checklist

• [ ] I have read the contribution guidelines
• [ ] Suitable unit/system level tests have been added and they pass
• [ ] Documentation has been updated
  • [ ] Upgrade instructions
  • [ ] Configuration details
  • [ ] Concepts
• [ ] Changes flowforge.yml?
  • [ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • [ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
• [ ] Link to Changelog Entry PR, or note why one is not needed.

Labels

• [ ] Includes a DB migration? -> add the area:migration label

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 76.22%. Comparing base (6755d2c) to head (8fcb4ca). :warning: Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6286   +/-   ##
=======================================
  Coverage   76.22%   76.22%           
=======================================
  Files         393      393           
  Lines       19777    19777           
  Branches     4741     4741           
=======================================
  Hits        15075    15075           
  Misses       4702     4702           

Flag	Coverage Δ
backend	76.22% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dimitrieh]

@cstns why not to 4.1?

[cstns]

v4 has a hard dependency of node >= v20 while our docs state that we support v18.

[hardillb]

We have moved the built containers to nodejs 20 and the tests iirc.

NodeJS 18 is now EoL so we really should drop it as dependency, but we need to check (and I need to convert my dev env over).

[cstns]

We're risking breaking things upgrading tailwind to 4.0 without making sure all on-premise installations have also done so. I'm fine with upgrading to 4.0 but we should make it clear that the next release will make node 20 mandatory (and also upgrade the docs)

[cstns]

spoke w @hardillb we can safely upgrade to 4.0, I'll add a changelog request announcing our minimum node version change and one for the docs to update the entry

[cstns]

Changelog request and docs update pr's are in place.

[dimitrieh]

Very nice! Well that opens the door than to V4: https://staticmania.com/blog/tailwind-v4-vs-v3-comparison

[dimitrieh]

@cstns I see you already upgraded to v4.0.0. Why not to the latest? https://github.com/tailwindlabs/tailwindcss/releases

PS: We can also look into https://tailwindcss.com/plus/ui-blocks#product-application-ui

[cstns]

I'd love a go at the settings pages with tailwind plus, worth getting in my opinion

[cstns]

I set a hard minimum allowed limit of 4.0.0 but 4.1.17 is installed and will match any 4.*.* version

[dimitrieh]

Fixed my commit signing :)