deps: upgrade to npm 3.7.2

[zkat]

Hey! Rebecca's out, so I'm doing the npm@3 thing this week.

This includes the following releases:

• https://github.com/npm/npm/releases/tag/v3.7.0
• https://github.com/npm/npm/releases/tag/v3.7.1
• https://github.com/npm/npm/releases/tag/v3.7.2

Notable changes:

• c680fa9 npmlog@2.0.2: New are-we-there-yet with performance patches from @STRML. New gauge with timer churn performance patch. This is the make-the-progress-bar-not-slow-stuff-down patch. (@iarna)
• 39dea9c #1876 (New Feature) Add support for git submodules in git remotes. (@gagern)
• doc and bug fixes

r: @Fishrock123
r: @jasnell
r: @mikeal
r: @thealphanerd

[MylesBorins]

@zkat should we close #5097 in lieu of this update?

[MylesBorins]

@jasnell do we want to land this on master or on v5.x?

[MylesBorins]

I have patched this on top of v5.x and the test suite passes.

#5212 just came in which removes some deps from the 3.6 release for having too long of a path. Just wanted to bring it to attention

/cc @mscdex

[zkat]

@thealphanerd Oh! Welp, that's why I failed to find it. My quick search for dep upgrades is deps: npm, and I didn't see anything after 3.6.0 so I assumed all three of these were there.

I'd say to have this one supplant that one, yes. At least that's what we've done with LTS releases.

[MylesBorins]

sgtm... closing the other one 😄

[MylesBorins]

CITGM run rebased against v5.x: https://ci.nodejs.org/job/thealphanerd-smoker/90/

edit: It looks like v3.7.3 is actually ready to come downstream. As such I'd like to advise that we close this PR and #5212 in lieu of the new PR @zkat is putting together right now which should fix npm on master. This PR should be cherry-picked to v5.x and included in the v5.7.0 release

/cc @rvagg @Fishrock123

[zkat]

Closing this one in favor of #5369.