fix: use literal envPrefix queries for Vite Task

[wan9chi]

Problem

The Vite Task integration reports envPrefix values to getEnvs as glob patterns like ${prefix}*. That creates a corner case where an envPrefix containing * is treated as a wildcard by the task client, while Vite itself treats envPrefix as a literal string prefix.

Solution

Use the literal prefix query form from @voidzero-dev/vite-task-client@0.2.0, added in voidzero-dev/vite-task#472, and call getEnvs({ prefix }) for each configured envPrefix.

Compatibility

This can move to the 0.2.0 client query form without released-compatibility fallout because no Vite Task release with vite-task-client client support has shipped yet. There is no released Vite Task version depending on the previous client query contract.

[sapphi-red]

Instead of using prefix, should we escape * like FOO\*BAR* (prefix is FOO*BAR in this case)?
That would be more expressive and can support suffix or wildcard in the middle.

[wan9chi]

I considered escaping on the Vite side, but that would require Vite to be aware of the full glob syntax supported by Vite Task (currently it's https://docs.rs/globset/0.4.18/globset/#syntax) and escape all the metacharacters correctly.

I think it's better to just let Vite express the intent here ("getting envs with this prefix"). Then Vite Task can handle the escaping internally alongside the glob implementation. That also leaves room for Vite Task to change the underlying matcher later, for example escaping to regex instead of glob, without breaking anything.