Move @types/node to dev dependencies

[cgewecke]

Description

#3412 redux (This is being re-opened on a local branch because the original PR was made directly from the 1.x branch of a fork and needed some maintainer edits -cg )

moving @types/node to a devDependency. It isn't needed at runtime, and if a library user is is targeting browser this dependency will give them incorrect type hints.

Fixes #2965

and re confirmation request of #3337

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• [] I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run dtslint with success and extended the tests and types if necessary.
• I ran npm run test:unit with success.
• I have executed npm run test:cov and my test cases do cover all lines and branches of the added code.
• I ran npm run build-all and tested the resulting file/'s from dist folder in a browser.
• [] I have updated the CHANGELOG.md file in the root folder.
• [] I have tested my code on the live network.

[cgewecke]

(From my previous review...)

"LGTM - the types tests import net from NodeJS and there's no other reference. "

[coveralls]

Coverage remained the same at 86.048% when pulling cf8db2d on cokia/node-types into d063437 on 1.x.

[cgewecke]

@holgerd77 You reviewed this as #3412 - have reopened it here addressing some concerns raised
about the scope of the package-lock changes.

[holgerd77]

LGTM

[cokia]

Thanks :)