Log segfaults in native modules.

When native code crashes, we don't get any kind of stack trace to help
us debug. At least dump a stack trace now.

Note: this uses a specific git commit of node-segfault-handler because
the released version does not work correctly with node 0.10.x.
A few locking changes

1. The Monitor class was essentially doing nothing because the scoped_lock objects weren't actually locking any supplied mutex.  Also, locking before a function call is a bad idea because the bounds of the lock are indeterminate, so do not lock there anymore.
2. Remove the writeMutex_ in WebRtcConnection; it was only protecting a single method that doesn't need protection
3. Remove some unused stuff.
Change WebRtcConnection to use webrtc's fec if necessary

because firefox doesn't support RED/FEC, licode was converting RED/FEC to raw VP8, but it was doing this for everybody, regardless of whether or not they could digest red.  change it so for endpoints that can digest red, we send it straight through.  For those that can't, we use WebRTC's FEC handling to recover missing packets.
Merge pull request #192 from jnoring/improvements

Improvements
Added queue and mutex for events in erizoAPI
Potentially, events could be lost
Load the segfault handler in erizoJSController.

Now that erizoJSController loads the native addon, the segfault handler
should be loaded here.
Merge pull request #191 from byronclark/segfault-handler

Log segfaults in native modules.
audioTransport was created and not needed when bundle
Fixed a bug when muting localstreams
Added stats for connection status in JS controller
Fixes in events
Not sending ok signalling messages
Merge remote-tracking branch 'upstream/master'