Add support for "outputs" for target's configuration

[TomasChmelik]

In my usecase I have a "build" target which has "dev", "test" and "prod" configurations. Each configuration specifies different value for environment variable. This variable is then read in vite.config.ts to configure where outputs will be put. If this env variable isn't defined, the "prod" is used as a fallback.

Problem is that each configuration has different output folder (based on that environment variable) because they could be built at the same time and they definitely have different content.

This means when Nx reads config of "build" target from vite.config.ts, it assumes the only output of this target is the "prod" output folder.

I can't use {options:foo} in the outputs path because this new option is not accepted by vite.

I suggest two possible solutions:

• Allow specify "outputs" for each configuration. It is open question if configuration's outputs should be merged with task's outputs or if it should override it all together. Either way it fine, as long as it would be documented.
• Allow use something like {configuration} variable in the outputs paths. Not ideal since configuration name might not match the folder name, but at least better than nothing.