Refactor Node.gitignore with comments

The "build" directory is lost in this refactor, as many JS projects
do wish to include a minified/concatenated version of their source
in the "build" folder in source control.
Clarify node_modules comment

Now linking to the official npm FAQ entry (with tl;dr) rather than straight to mikeal's blog post
Add build/Release to Node gitignore

This re-covers the http://nodejs.org/api/addons.html case for which the "build" directory was added in 00686415c4, but doesn't break cross-environment projects that use the build directory for including concatenated/minified source. Mazel tov!
Add `coverage` directory, rename coverage heading
Add .grunt directory
Node.gitignore: correct term for instrumentation
Merge Sass and Compass templates
Remove old sass-cache rule for Rails
Adding the EiffelStudio .gitingore file.
Enable Ignore of NuGet Packages Folder By Default

Submitting this for consideration.

The first thing that I do on every new project is to go in and uncomment the packages folder. With the prevalence of NuGet and prominence of its use in the Visual Studio environment, along with how well package restore *just works* now, I believe this should be the default.

While I understand that package restore isn't on by default, I would argue that the types of developers using NuGet _and_ a distributed SCM are the types of developers that would omit the binaries from source control.
Move the EiffelStudio.gitignore in the Global directory
Merge pull request #945 from arcresu/sass-cache

Simplify sass cache rules
Merge pull request #963 from tioui/eiffelstudio

Adding a global template for EiffelStudio
Merge pull request #969 from MisterJames/VisualStudioIgnore

Enable Ignore of NuGet Packages Folder By Default
Merge branch 'master' of https://github.com/github/gitignore into stuartpb-node-patch

Conflicts:
	Node.gitignore
Reduce comments
Merge pull request #913 from stuartpb/node-patch

Refactor Node.gitignore with comments
Remove Results classes from Node gitignore

These aren't really common patterns in the Node world, and if a Node project includes one of these types as files, they're as likely to want to include them in the project as not (`*.csv` is as likely to be a data source as `*.json`).
Fix comments in Dart.gitignore

.gitignore uses `#` for comments, not `//`
Rename IgnorePackages back to VisualStudio.gitignore.