Bump Libsass to 3.2.3

Load am11/pangyp from HTTPS

Update README.md

Libsass now allow us to add the missing compact and expanded output styles.

Remove use of 'package' as a variable name in install.js

Bump 3.0.0

build: Adds win_delay_hook so iojs runs with alias

Before building, first apply the following patch
to pangyp: rvagg/pangyp#5 (until it is merged).

Issue URL: #870.

Improve binary file download error handling

Do not throw exception on invalid/mangled URL
Provide consistent error message with the URL
on all failures.

Watcher should prioritize cwd when resolving imports

Create a troubleshooting guide

Bump Libsass to 3.2.2

Respect the LIBSASS_EXT build flag when falling back to git

Fix #912: Use runtime libsass version

Return real libsass version
information - in when a shared library
is used this version may be changed
even without recompilation

libsass version in the package.json
file is now used only for checking
out the bundled libsass library
from the git submodule

Bump Libsass and sass-spec to 3.2.0

Set User-Agent: HTTP header

Introduce SASS_BINARY_SITE environment and refactor API tests

Pin to nan@^1.8.4

Separate testing of all configuration
and runtime paramenters into a separate file.

Reduce bolierplate code and
use startup/teardown to restore
test context.

Implement additional single-parameter
tests for configuration variable.

Provide ability to locally mirror node-sass
binaries for various versions and platforms.

SASS_BINARY_SITE needs to be an URL pointing to
a collection of files organized like the Github
repository.

If SASS_BINARY_SITE is set to

 http://myhost:8080/local/node-sass-bin/

then

 http://myhost:8080/local/node-sass-bin/v3.0.0-beta.5/freebsd-x64-14_binding.node

should point to the FreeBSD 64 bit binary for node 0.12.0

The URL can be also specified as the --sass-binary-site
commandline option or in the package.json:

 "nodeSassConfig": {
   "binarySite": <url>
 }

Remove --sass-binary-url and friends.

Also change priority and use package.json defaults
last, after command line arguments and the environment.

Show expected binary path in the error message if bindings not found

Kill watcher processes during test

After running npm test four node processes
keep on running:

85880  1  S        0:00,41 node node-sass/bin/node-sass --watch node-sass/test/fixtures/simple/tmp.scss
85883  1  S        0:00,41 node node-sass/bin/node-sass --watch --quiet node-sass/test/fixtures/simple/tmp.scss
85885  1  S        0:00,40 node node-sass/bin/node-sass --output-style compressed --watch node-sass/test/fixtures/simple/bar.scss
85888  1  S        0:00,42 node node-sass/bin/node-sass --output-style compressed --watch node-sass/test/fixtures/watching/index.scss

We need to explicitly kill them when the test is done.