- npm package file

Super basic setup of the NPM file using `npm init` as a start for our
Grunt tasks.
- adding grunt and grunt cli modules

We will need the Grunt and Grunt CLI node modules to start building with
Grunt and here they are.
- adding the grunt sass module

This module is what hooks up our Sass processing gem (it's a ruby term)
to Grunt so we can build the Sass files.
- adding the watch module

The watch module allows us to watch files and do auto-building of
items as they change.

So as I'm working on the Sass stuff that means I can run the `grunt
watch` command and then as I change Sass files Grunt will auto-build
things for me.

Of course that means I'll need to build the watch and sass tasks shortly
as well.
- all the npm packages

An awesome part of using grunt/node is that now we have the proper
packages defined in our package.json build files so when another dear
dear developer comes along they also have them.

Awesome eh?
ignoring the sass cache file since we do not really need to trade it around
- our starting grunt build process

This commit has a validated build process (and watch commands) running
for our Sass.

Now you can runn `grunt watch` and that will give you a terminal task
that watches the sass files and builds them.

Right now it's only the one file, but next up is adding all the other
CSS files that we need.
- basic Sass build validations

So far this just moves the stock admin-styles.css file and adds .scss
and then builds it back to it's old location.