Implement HasteUpdateServer

1. Long running process for updating resource maps
2. Can run for multiple haste instances and resource maps
3. When a file changes it will be swapped out in our in-memory file list to be analyzed and updated on disk
4. Maps are persisted back to disks
5. A net server starts for querying status

Designed to be used by CLIs to start the server if not started. Will probably need a few changes come _real_ integration time (done some testing on devservers)
It does seem more efficient to update the map directly on fs change events, but on the other hand it feels like we're reaching into contracts from within node-haste internals to do so. It might be simpler (here in this code + in the future if node-haste ever changes) to just debounce updates/re-run the haste updater on some slow interval.

Thoughts?