doc: update LICENSE file

[Trott]

Running license-builder.sh seems to indicate that there have been some
license changes that have not been propagated to our LICENSE file yet.
Here they are.

@richardlau

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• 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/125/pipeline

[Trott]

Anybody know what's up with the http_parser license text that is removed?

[bnoordhuis]

@Trott nodejs/http-parser@89279ab

[Trott]

👍 here for fast-tracking.

[richardlau]

Thanks for updating. Perhaps in another PR we can consider how to keep things in step, either as a test or part of the build process.

[ChALkeR]

@Trott is there any reason why we shouldn't be just running license-builder.sh on CI and comparing the output with LICENSE file to catch license changes in the commits that introduce those?

Will it make backporting harder?

[Trott]

@Trott is there any reason why we shouldn't be just running license-builder.sh on CI and comparing the output with LICENSE file to catch license changes in the commits that introduce those?

Seems like a good idea to me. Or write a test that does that so it can be caught during make test....

Will it make backporting harder?

I don't see how, but there could be something I'm missing.

[Trott]

Landed in 1e7ff81

[ChALkeR]

@Trott

Or write a test that does that so it can be caught during make test.

That's what I meant :-).