Enabled workaround for localStorage

Access to localStorage does not work once „Block third-party cookies
and site date“ is enabled. This is a workaround based on
https://code.google.com/p/chromium/issues/detail?id=178618#c25
Updated manifest to include background-script
Spaces instead of tabs, backwards compatibility

Made use of the localStorage key „flo-config“ which should guarantee
backwards compatibility.
Proper backwards compatibility

So I had missed that the background page is a page of its own of course
and thus with a localStorage of its own. Now that’s taken in
consideration and fixed.
tabs to spaces
removed .editorconfig
On windows, the file path contains back slashes

Ensure that resourceURL is transformed to replace back slashes with
forward slashes
Handle and emit errors from Watcher

This prevents the Flo session from crashing, making it more resilient,
and gives consumers of Flo the opportunity to handle watcher's errors.
Remove my original fix for windows paths

Given that it has been properly refactored
redirect errors to flo from watcher
Add to doc info regarding `fb-flo-reload` event, implements #53

Added information regarding the `fb-flo-reload` event, that is fired upon any resource updating, to the README.md file. (implementing #53)
Included short example of how the `fb-flo-reload` event can be used
Proposal: Executing client-side code as part of the callback
Executing client-side code as part of the callback - added suggestions and example in the documentation
Added href fallback for hostname when determining location.
Adding repository field to package.json

Otherwise it throws a warning.