Updates to use Mincer 1.0.5

It seems like there were a few reasons a lot of tests were failing when upgrading to Mincer 1.0.5 (#239)
- Compile changed from a callback to a sync format
- Hashes at the end of files changed

### Assets/Connect-Assets
1) The change to account for the now sync nature of compile is handled by invoking the callback with ```null, manifest``` where manifest is the return from compile. 
Since errors in compile will now throw an error that was wrapped in a try/catch and the callback is invoked with the error.

2) Changed the cssCompressor to ```csswring``` for sourcemap support.

### Tests
1) Updated tests with new hashes. Test suite was run on another's machine to ensure they were the same across test runs and machines.

2) ```compiles only those listed in --compile ``` would only generate 2 files. The ```.gz``` file was not generated. Is this something mincer handled before? If so can you shed some light on what the process was

3) All tests pass except 1: ```serveAsset manifest uses an existing manifest if it exists``` 
The manifest that exists is overwritten with the actual manifest.
What should happen for this test? Not sure if functionality changed between versions of mincer around this.

Deal. 

I’ve written most of the tests to have hardcoded md5 fingerprints, mainly because sometimes you change something in code, and it’s nice to know when you’ve touched the output of a file (sometimes unexpectedly). 

It does make things like upgrading mincer versions a bit of a pain in the ass though, since you have to touch all those md5s. 

I’m +1 on using the manifest here though, as the other tests should capture any unexpected file contents changing.