fix: ignore node prereleases in npm engines check

[wraithgar]

They don't currently have any so that code would never have mattered

cf https://nodejs.org/download/release/

[wraithgar]

Gonna have to get clever in the test fixture

[npm-cli-bot]

no statistically significant performance changes detected

timing results

app-large	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit	show-version	run-script
npm@9	35.080 ±2.38	19.409 ±0.05	19.039 ±0.03	21.248 ±0.09	3.102 ±0.03	3.092 ±0.03	2.661 ±0.07	12.900 ±0.03	2.577 ±0.04	3.849 ±0.16	0.434 ±0.01	0.473 ±0.01
#6574	36.029 ±2.91	19.850 ±0.06	19.220 ±0.20	21.622 ±0.14	3.071 ±0.01	3.165 ±0.03	2.631 ±0.00	13.195 ±0.12	2.591 ±0.01	3.754 ±0.11	0.455 ±0.01	0.504 ±0.01

app-medium	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit	show-version	run-script
npm@9	26.570 ±1.48	15.170 ±0.04	14.745 ±0.24	15.886 ±0.09	2.779 ±0.05	2.797 ±0.01	2.522 ±0.08	9.800 ±0.28	2.395 ±0.02	3.426 ±0.12	0.426 ±0.00	0.475 ±0.00
#6574	26.162 ±1.48	15.339 ±0.11	14.850 ±0.05	16.162 ±0.16	2.812 ±0.00	2.874 ±0.03	2.561 ±0.04	10.165 ±0.10	2.432 ±0.01	3.399 ±0.00	0.447 ±0.01	0.510 ±0.01

[wraithgar]

https://nodejs.org/download/release/

Do we even need the flag at all?

[lukekarrys]

https://nodejs.org/download/release/

Do we even need the flag at all?

At the risk of prematurely optimizing, if Node ever did ship a prerelease we would want that flag (and the template-oss PR). So I think for the sake of having the code match our intent (even if it's not currently possible), we should land both PRs.