Remove npm install because it uses legacy Python

[cclauss]

Fixes #1977 (comment)

Checklist

• npm install && npm test passes
• tests are included
• documentation is changed or added
• commit message follows commit guidelines

Description of change

[sam-github]

What does this fix? Is there a nodejs or https://github.com/felixrieseberg/windows-build-tools/issues bug it refers to?

The manual install of C++ build tools is pretty finicky. /cc @gireeshpunathil who has helped people work through issues with Windows setup a fair bit.

[cclauss]

Fixes: #1977 (comment)

[just-boris]

@sam-github this can serve as a relevant report in the other package: felixrieseberg/windows-build-tools#191 (comment)

[sam-github]

Is this obsoleted by felixrieseberg/windows-build-tools#205 @cclauss ?

[cclauss]

That PR currently fails its tests and I do not know how to get them to pass. If it did pass those tests and was merged then we could close this PR without merging these changes.

[richardlau]

That PR currently fails its tests and I do not know how to get them to pass. If it did pass those tests and was merged then we could close this PR without merging these changes.

I think you'll need to remove the check for ' 2.' in https://github.com/felixrieseberg/windows-build-tools/blob/b4c681c770fa429734e45600906b4271421e1328/src/utils/get-is-python-installed.ts#L13-L17

[rvagg]

I'm uncertain of the status here, it seems like it might have been made redundant? that file now checks for 3. https://github.com/felixrieseberg/windows-build-tools/blob/master/src/utils/get-is-python-installed.ts#L13-L17, I suppose that's better