Interactive `tailwind:init`

[kbond]

Idea from @mahono in #93.

When run, ask the following questions:

• Are you managing your own Tailwind CSS binary?
  • Yes?
    • Path to binary? (set this in config and run normal init logic)
  • No?
    • What major Tailwind CSS version would you like to use (3/4)? (set this in config and run normal init logic)

Then, we could remove the recipe config (which currently hard-codes a version) and not let you run tailwind:build until you run tailwind:init (or configure yourself)