test: fix test-cli-syntax assertions on windows

[not-an-aardvark]

The test introduced in a5f91ab accidentally introduced failures on some windows builds. Update the assertion that was causing the failures.

Ref: #11689

Checklist

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

Affected core subsystem(s)

test

[not-an-aardvark]

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

[gibfahn]

We should land this ASAP (once CI passes) to fix CI on windows master.

cc/ @nodejs/platform-windows

[refack]

I hate the \r\n EOF mess.

[bzoz]

LGTM if the CI is green

[Trott]

This LGTM as-is, although I think I'd prefer assert.strictEqual(c.stderr.trim(), ...);. That would provide a more helpful message in the event that the assertion fires.

[not-an-aardvark]

@Trott I agree that would have been better, but for now I think I'm going to land this as-is so that the build on master can be fixed ASAP. I can follow up with another PR to improve the error message.

[not-an-aardvark]

Landed in 9348f31

[italoacasas]

cc @not-an-aardvark

[not-an-aardvark]

This fixes a bug that was introduced in a semver-major commit -- it doesn't seem like it makes sense to backport.