Removed LZString (major performance issue in IE) & replaced with new Pako library && MAJOR CHANGE added db.js for conversion of cache from localStorage to Indexeddb

- Stripped LZString deps due to IE >800 ms load inclusive run time on
larger string sets

- Pako was faster and helped keep the JS memory lower (important for
other IE perf issues)

- DB.js wraps indexedDB with a Promise API to give us a very fast/clean
object store without the needs for JSON or compression (size is user
controlled and they are automatically notified if increase is needed).
Updated ftss.jade to match globals placement in index.jade
Renamed _mixins.jade to __mixins.jade to prevent Brunch from ignoring it when watching the directory
Tweaked utils.log() for IE (which just does a dumb toString() on objects unlike Chrome/FF)
Updated utils.compress()/decompress() to use Pako instead of LZString
Refactored postProcess() & mainController watchers/permaLink() code

- Much better/consistent control of how the async events fire in
postProcess w/ability to prevent accidental duplicate calls

- Fixed some watchers not firing when they should

- Added equality check to doProcess() as well to prevent extra fires
OPTIMIZATION: 80% reduction in page load time, Completely rewrote the caching functions within Angular-Sharepoint

- Dropped JSON serialization requirement

- Dropped LZString/string compression requirement

- Implemented IndexerDB instead using db.js
(https://github.com/aaronpowell/db.js)

- Added loader queue to handle the async db setup (for some reason IE
is actually a lot faster at this than Chrome and it was causing issues
on the dev machine)

- Updated _config to be more dynamic for switching between localhost &
192.168.1.2 (remote access to VM)

- Fixed weird duplicate call to new Date() in _utils.getTimeStamp()

- Code formatting stuff, dumb WebStorm…

- Added _debounce{} object to prevent multiple calls to the same
resource with N number of seconds (currently hard-coded to 15 but will
move to config later on)

- Refactored cacheString into  _utils.cacheString() — this will be
useful later on

 - Saving back to cache is also async now so we fire and forget it to
continue loading the page