feat: allow http-parser NODE_OPTION in packaged apps

[codebytere]

Description of Change

Closes #21693.

Whitelists --http-parser=parser for use in packaged apps. As a rule, we only allow NODE_OPTIONs in packaged apps on a case by case basis, but as stated in the above linked issue, Node v11.5.0 changed the default HTTP parser to one that breaks some use cases (see comment), and so that presents a compelling case for allowing this particular flag.

cc @MarshallOfSound @ckerr @zcbenz

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• relevant documentation is changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Changed NODE_OPTIONs to allow --http-parser to be used in packaged apps.

[release-clerk]

Release Notes Persisted

Changed NODE_OPTIONs to allow --http-parser to be used in packaged apps.

[natkrish]

Can someone please let me know on when this will be released?

[codebytere]

/trop run backport-to 8-x-y,9-x-y

[trop]

The backport process for this PR has been manually initiated -
sending your commits to "8-x-y"!

[trop]

The backport process for this PR has been manually initiated -
sending your commits to "9-x-y"!

[trop]

I was unable to backport this PR to "8-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "9-x-y" cleanly;
you will need to perform this backport manually.

[trop]

@codebytere has manually backported this PR to "8-x-y", please check out #22539

[jkleinsc]

The Releases WG has approved this for backporting to 8-x-y.