Importing a fresh copy of graceful-fs then using `require('fs').close`
would only initiate retry of the queue from the first copy of
graceful-fs, so needed retries associated with subsequent instances of
graceful-fs would not be executed.

Some changes in the previous commit are not needed in v4.x which will
never be tested under nyc.  The only thing needed is the ability for the
next version of graceful-fs to reset fs.close / fs.closeSync.

This was for an issue with versions of node.js that are EOL.
Node.js commits which fixed this issue:
* v4.6.2+ - nodejs/node@3d6f107a2f
* v6.8.0+ - nodejs/node@07d97f4f3e
* v7.0.0+ - nodejs/node@3d6f107a2f

Also remove associated testing.

Properly handle DEP0013 in ENFILE/EMFILE patched functions depending
on node.js version.

* Add autoClose support to WriteStream.open
* Prevent accidental monkey-patching of fs.*Stream

Properly handle DEP0013 in patched fs.close.

Process callback argument to ensure proper handling if missing.

* Create windows-rename-polyfill.js
* Eliminate process.env.GRACEFUL_FS_PLATFORM
* Modernize windows-rename-polyfill test

* Prefer const
* Space before function parentheses
* Remove unused args

* Avoid process.binding
* Monkey-patch promises FileHandle.close to call retry
* Do not use promisify
* Eliminate delay on first open