lib: fix segfault with --without-intl

[Trott]

Node.js segfaults when build with --without-intl due to an oversight
in d13cdd9. This fixes the issue.

This is an alternate to #21587 and was proposed in IRC by @devsnek and also @refack. But @devsnek doesn't have access to GitHub right now, so I'm submitting it to fast-track it and get CI green again.

Speaking of which: 👍 to fast-track.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[nodejs-github-bot]

@Trott build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/174/pipeline

[Trott]

CI: https://ci.nodejs.org/job/node-test-pull-request/15665/

[Trott]

@nodejs/releasers What is your preference for how to do these kinds of things? Revert the offending commit and then re-land? Or a patch fix like this one is fine? Or it doesn't matter either way?

[Trott]

(The revert commit causes a test to fail so it will take some tweaking if we want to go that route. So I'd prefer this PR over a revert at this point...)

[Trott]

Resume Build for CI: https://ci.nodejs.org/job/node-test-pull-request/15667/

[Trott]

arm-fanned Rebuild: https://ci.nodejs.org/job/node-test-binary-arm/2095/

[Trott]

arm-fanned rebuild (https://ci.nodejs.org/job/node-test-binary-arm/2095/) is green.

Just waiting for node-test-commit-linux to finish. Everything is green except fedora-latest-x64 which will hopefully be finished running in another 10 minutes or so....

[refack]

https://ci.nodejs.org/job/node-test-commit-linux/19844/nodes=fedora-latest-x64/console is stuck.
Re-run - https://ci.nodejs.org/job/node-test-commit-linux/19847/

[Trott]

https://ci.nodejs.org/job/node-test-commit-linux/19844/nodes=fedora-latest-x64/console is stuck.

@refack For what it's worth, I often find the console on that shows the querystring.json line in compile for a half hour or more, and then suddenly finishes all at once, like it's buffering the entire console.

Always stops on querystring.json or somewhere near that. Can take up to an hour and twenty minutes and still come back green. Sometimes it only takes 12 minutes though. So...
¯\(ツ)/¯

[Trott]

@refack: It's doing it right now...stuck at all.json and will probably stay there for several minutes or longer, then suddenly everything will appear all at once. https://ci.nodejs.org/job/node-test-commit-linux/19847/nodes=fedora-latest-x64/console

[refack]

I've seen that... But it was at 37 minutes, and it felt unhealthy...
We should figure that thing out...

[Trott]

The one host under Linux that wasn't green was green this time. There is another host that is taking a long time, but that platform was green last time. Given the CI situation and the fast-track approval, I think piecing together a green CI from different places like that is acceptable. I'm going to land this. (Plus, this is easy to revert since it's a one-line change.)

[Trott]

Landed in 1c30343