fix(core): handle FORCE_COLOR=0 with picocolors (#34520)

## Current Behavior

After migrating from chalk to picocolors (#34305), `FORCE_COLOR=0` no
longer disables colors. picocolors checks `!!env.FORCE_COLOR`, and since
`!!"0"` is `true` in JavaScript, it treats `FORCE_COLOR=0` as "enable
colors."

This breaks CI environments and tools like Homebrew that set
`FORCE_COLOR=0` to get plain text output.

## Expected Behavior

`FORCE_COLOR=0` should disable ANSI color output, matching the previous
chalk behavior and the [FORCE_COLOR spec](https://force-color.org/).

## Related Issue(s)

Fixes #34387

Upstream issue filed:
alexeyraspopov/picocolors#100

(cherry picked from commit f31e7a7)

Author: FrozenPandaz

packages/nx/bin/nx.ts

@@ -1,4 +1,12 @@
 #!/usr/bin/env node
+
+// TODO: Remove this workaround once picocolors handles FORCE_COLOR=0 correctly
+// See: https://github.com/alexeyraspopov/picocolors/issues/100
+if (process.env.FORCE_COLOR === '0') {
+  process.env.NO_COLOR = '1';
+  delete process.env.FORCE_COLOR;
+}
+
 import {
   findWorkspaceRoot,
   WorkspaceTypeAndRoot,