[release] Allow building single release channel with processed versions

[eps1lon]

Local yarn build always built experimental and stable locally. However, that's not always necessary. E.g. yarn build-for-devtools only needs experimental but you had to wait for stable to finish as well.

CI should be unaffected. --release-channel was already supported with --ci.

[react-sizebot]

Comparing: 09f0569...f8383be

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.js	=	6.84 kB	6.84 kB	=	1.88 kB	1.88 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	=	608.36 kB	608.36 kB	=	107.68 kB	107.68 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.84 kB	6.84 kB	=	1.88 kB	1.88 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	667.47 kB	667.47 kB	=	117.57 kB	117.57 kB
facebook-www/ReactDOM-prod.classic.js	=	693.67 kB	693.67 kB	=	122.07 kB	122.06 kB
facebook-www/ReactDOM-prod.modern.js	=	684.10 kB	684.10 kB	=	120.45 kB	120.45 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against f8383be

[poteto]

do we need to update any of the GH action workflow files too?

[eps1lon]

They should be unaffected since they run with --ci which doesn't enter the changed codepath:

react/.github/workflows/runtime_build_and_test.yml

Line 362 in 09f0569

- run: yarn build --index=${{ matrix.worker_id }} --total=25 --r=${{ matrix.release_channel }} --ci

Other invocations of yarn build in the repo don't use --release-channel, -r, --release_channel, or --release_channel

[poteto]

thanks for confirming!