added support for lockfileVersion 3

[Airdevelopments]

This might be handy for people who updated from an old lockfileVersion 1 to lockfileVersion 3 immediately (skipping lockfileVersion 2).

Requesting a review of the changes, since I am not really certain of the differences between lockfileVersion 2 and 3.

[webstech]

This might be handy for people who updated from an old lockfileVersion 1 to lockfileVersion 3 immediately (skipping lockfileVersion 2).

On what version of npm did you find this problem? I ran a test on npm 9.1.1 and it set hasInstallScript during auto-upgrade of the lockfile from v1 to v3.

Requesting a review of the changes, since I am not really certain of the differences between lockfileVersion 2 and 3.

From the doc, v2 is a compatibility format containing both the v1 and v3 information.

[Airdevelopments]

It was one of the recent npm versions (9.6.5 I think.). It only involved packages from 3rd party package registries using authentication (fontawesome and an internal one via gitlab).

We updated from node 14 to 18 and npm 5 or 6 to 9 (and the lockfiles with that).

Packages like electron via the public npm registry did not run into any issues adding the install scripts flag to the lockfile.

I will try to create a small repo to reproduce the issue if necessary (but might take a week or two since I don't have the time available rn).

Thank you for answering the pull request.

Best Regards.