Show warning when using unsupported bare value data type

[RobinMalfait]

This PR will show a warning if you are using a bare value data type that is not supported.

Let's say you want to create a new utility that allows color to be a bare value data type like this:

@utility paint-* {
  paint: --value([color], color);
}

This means that this would enable new syntax that we don't support yet. E.g.: paint-#0088cc.

The only supported data types for bare values are:

• number — 2.5
• integer — 2
• ratio — 1/2
• percentage — 50%

All other data types are not supported in this position. This PR will now show a warning:

Unsupported bare value data type: "color".
Only valid data types are: "number", "integer", "ratio", "percentage".

```css
--value([color],color)
                ^^^^^
```

Once we have better sourcemap / location tracking support, this warning will point to the exact spot, but for now, only a re-print of the AST can be used.

If you do want to use other data types, then you will have to use arbitrary value syntax with […] instead.

@utility paint-* {
  paint: --value([color]);
}

This will allow for paint-[#0088cc] for example.

Note: this is not a behavioral change, we already didn't support other data types, but we silently ignored them. This means that we have to do more parsing at runtime when evaluating the utility.

With this change, a warning is shown when registering the @utility, not when using it.

[RobinMalfait]

@adamwathan do you want to make any changes to this warning?

Output looks something like this right now:

Unsupported bare value data type: "color".
Only valid data types are: "number", "integer", "ratio", "percentage"

```css
--value([color],color)
                ^^^^^
```

[philipp-spiess]

My 5 ct: I don't think the term "bare value" is something that people of that API will be familiar with but maybe we just call it "value data type" (since it's the --value(…) function)?

Unsupported value data type: "color".
Only valid data types are: "number", "integer", "ratio", "percentage".

```css
--value([color],color)
                ^^^^^
```

The rest I think is fine personally but I'd add a dot at the end of the second sentence

[RobinMalfait]

I think people writing plugins like that will be more familiar with the term (or at least should be because they will have to know the difference between color and [color]).

Main reason I used it is because that's what we use in the docs for it: https://tailwindcss.com/docs/adding-custom-styles#bare-values

[philipp-spiess]

Ohh right we do refer to it like that in the docs huh, yep then I think this does make sense