Better module init
Added CPU and Memory reporting / guarding

There are various reasons that can make pilight spike in CPU
resources. The prevent the system to become unresponsive,
pilight will now check its own CPU and memory usage.
If pilight is using > 75% CPU over 10 seconds, it
will gracefully close itself. If pilight reaches over 90% CPU
it will force exit itself. The same counts for memory usage.

When we know this information, it can also be used to create
more information about pilight itself. So an additional
built-in protocol has been created that communicates the
pilight CPU and Memory usage every 5 seconds.
Added bye bye standbye to the devices list
Made cpu usage more accurate and added it to the webgui
Fixed bug in which state changes weren't communicated
Ram and cpu stats only displayed with websockets
Fixed some compilation warnings
Some updates to the cmake configuration
Reset high CPU / RAM flags
Updated webgui jQuery (1.3.2 --> 1.4.2)
Reverted the relative footer condition
Added timeout in socket connect function
Also give 90% CPU and RAM 10 seconds to settle
This commit adds a thread cpu usage profiler.

The upcoming pilight version will contain a CPU / Memory watchdog.
When the CPU reamains too high, pilight will stop or terminate.
The only issue is that we didn't know what actually caused the
CPU spikes. A new feature was added that checks the CPU usage
of each individual thread. This makes debugging a lot easier.

This report will be generated whenever the CPU usage is above 70%

[Jun 03 15:16:53:949607] pilight-daemon: ERROR: ----- Thread Profiling -----
[Jun 03 15:16:53:950010] pilight-daemon: ERROR: - thread lirc: 0.028586%
[Jun 03 15:16:53:950358] pilight-daemon: ERROR: - thread dht22: 0.000000%
[Jun 03 15:16:53:950836] pilight-daemon: ERROR: - thread openweathermap: 0.000000%
[Jun 03 15:16:53:951135] pilight-daemon: ERROR: - thread rpi_temp: 0.000000%
[Jun 03 15:16:53:951614] pilight-daemon: ERROR: - thread sunriseset: 22.176795%
[Jun 03 15:16:53:952145] pilight-daemon: ERROR: - thread program: 0.000000%
[Jun 03 15:16:53:954759] pilight-daemon: ERROR: - thread xbmc: 0.115843%
[Jun 03 15:16:53:955259] pilight-daemon: ERROR: - thread second parser: 0.017591%
[Jun 03 15:16:53:959918] pilight-daemon: ERROR: - thread socket: 0.000000%
[Jun 03 15:16:53:961852] pilight-daemon: ERROR: - thread ssdp: 0.000000%
[Jun 03 15:16:53:962156] pilight-daemon: ERROR: - thread sender: 0.000000%
[Jun 03 15:16:53:966543] pilight-daemon: ERROR: - thread broadcaster: 0.000000%
[Jun 03 15:16:53:966892] pilight-daemon: ERROR: - thread updater: 0.065168%
[Jun 03 15:16:53:967219] pilight-daemon: ERROR: - thread 433gpio: 48.632867%
[Jun 03 15:16:53:973839] pilight-daemon: ERROR: - thread receive parser: 0.002599%
[Jun 03 15:16:53:974269] pilight-daemon: ERROR: - thread webserver worker #0: 0.041879%
[Jun 03 15:16:53:978243] pilight-daemon: ERROR: - thread webserver client: 0.157222%
[Jun 03 15:16:53:982225] pilight-daemon: ERROR: - thread webserver broadcast: 0.013493%
[Jun 03 15:16:53:985941] pilight-daemon: ERROR: - thread firmware upgrader: 0.016392%
[Jun 03 15:16:53:986263] pilight-daemon: ERROR: ----- Thread Profiling -----
[Jun 03 15:16:53:990671] pilight-daemon: ERROR: cpu usage too high 70.402348
[Jun 03 15:16:53:993687] pilight-daemon: ERROR: checking again in 10 seconds
Small fix in the cmake file
Improved cpu usage detection and added noise detector
Updated Quigg protocol
Fixed bug in config in which unupdated values were communicated
Fixed small bug in log library
Fixed small bug in CMakeLists