Enabling Tailwind should enforce hot deploy mode

[sissbruecker]

Describe your motivation

Currently enabling the Tailwind feature flag just results in a new dev bundle being built. However, that doesn't help when developing an application:

• Adding new Tailwind classes to Java code does not trigger a new dev bundle
• Nor do I want to create a new dev bundle every time I add a new class name

The only way to make Tailwind useful during development is hot deploy mode so that every change in a Java file immediately triggers the Tailwind compiler to generate new CSS.

Describe the solution you'd like

Flow should automatically enforce hot deploy mode when the Tailwind feature flag is enabled. Also consider logging an info message that explains why hot deploy mode was enforced.

Describe alternatives you've considered

We document that using Tailwind also requires enabling hot deploy. However, that doesn't seem very helpful as Tailwind is essentially useless with dev bundles.