Overload Protection

Since PR: https://github.com/andytill/erlyberly/pull/112

erlyberly will suspend tracing when it detects an overload, that traces are being sent faster than they can be sent to the UI by the erlyberly process on the remote node. Detection is done by checking the process message queue, if the number of queued messages is higher than the number configured in the maxTraceQueueLength property in the .erlyberly2 configuration file then dbg is stopped, a trace suspended message is sent to the UI and the queued traces are sent to the UI, limited to maxTraceQueueLength.

The number of functions that will show in erlyberly will be half of maxTraceQueueLength because the call and return of the function are separate messages.