Switch to use standard @types/node types instead of our customized version

Using a custom version of the node typings is causing a lot of pain while trying to upgrade our build to use `@types` instead of the `d.ts` files we have to maintain. I believe we primarily maintain our own version for two reason:

- Custom require function
- setTimeout and other timer functions return NodeJs.timer instead of a number

These can both be delt with, the first by using interface augmentation and the second by switching to use any types for timer. I believe that the pain of maintaining our own node `d.ts` outweighs the benefits here

This change switches us to use the standard @types/node package for our node typings

src/vs/workbench/api/node/extHostStatusBar.ts

@@ -22,7 +22,7 @@ export class ExtHostStatusBarEntry implements StatusBarItem {
 	private _color: string | ThemeColor;
 	private _command: string;
 
-	private _timeoutHandle: number;
+	private _timeoutHandle: any;
 	private _proxy: MainThreadStatusBarShape;
 
 	private _extensionId: string;
@@ -173,7 +173,7 @@ export class ExtHostStatusBar {
 	setStatusBarMessage(text: string, timeoutOrThenable?: number | Thenable<any>): Disposable {
 
 		let d = this._statusMessage.setMessage(text);
-		let handle: number;
+		let handle: any;
 
 		if (typeof timeoutOrThenable === 'number') {
 			handle = setTimeout(() => d.dispose(), timeoutOrThenable);