Always build in the build directory

We can use deploy tasks to build into various directories based
on the version of the repository we have checked out. For standard
use, things should always build in one location locally.
Remove trailing commas in Gruntfile.js to be consistent
Convert other uses of build/version/ to build/, move demo.html
Remove demo.html

One of the reasons demo.html exists in the root of the repository
is because of the versioned build directory. This is no longer
necessary as build/ will be deployed to the tagged location.
Force HTTPS in a few other places
Can now use relative links for demo.html in build directory
Use develop as build_version in develop branch

This is the one portion that we'll need to maintain across versions
so that the compiled files inside the repository can reference the
proper build_version when the build is created.
Merge pull request #112 from washingtonstateuniversity/update/spine-build

[PR] Update Spine build process to be available for multiple deployed versions
Modify more asset URLS to be relative to location during demo and testing
Merge pull request #113 from washingtonstateuniversity/dev-ssl

[PR] Modify more asset URLS to be relative to location during builds
Remove extra line to test deployment of develop branch
Add UTF8 Charset definition at the top of all scss files

In production, we're seeing an error when grunt runs around an
invalid charset
Merge pull request #115 from washingtonstateuniversity/utf8

[PR] Add UTF8 Charset definition at the top of all scss files
Add CSS Map files to gitignore
Remove trailing slashes from location to avoid double slashes in URLs
Refactor sass global locality and introduce font_domain

Locality was hard coded to spine version 1 and not used everywhere.

I updated locality to point to the current develop version. We'll
need to determine the best way to track this for release going
forward. If we can pass in something from grunt, that would be ideal
so that we aren't jumping around looking for versions to bump.

Locality can always be https, because loading assets via https is
not a bad thing.

font_domain requires a relative URL as browsers have issues with
CORs requests, even across scheme
Merge pull request #117 from washingtonstateuniversity/deploy-tweaks

[PR] Adjustments around deploying from the develop branch
The test background image can now be relative to the page load
The test background image can now be relative to the page load
Use full repo URL as location instead of config.build

The mix of local and live wasn't working well here. Links in
production were referencing the local build directory and causing
confusion in general.

For now, I'm switching everything to repo.wsu.edu. It would be
nice if this location could change if a dev environment is in play.