Added public device API, overhauled event API and added autoconnect

- Added append() and loadScript() methods to common/Connichiwa.js, which allow to append HTML code or load JS on a remote device with a single method call
- The same methods are now available for every CWDevice
- The Event/Message API has been overhauled
	- Every received message triggers a “message”+message.type event
	- Framework-internal messages that web applications need to know about trigger high-level events. For example, a wasPinched message will trigger the “messagewasPinched” event, but also a “wasPinched” event. Registering for any event will be sufficient. The additional event is just for abstraction sake, so internal messages do not need to be known by the web developer
	- CWEventManger.register(), and in turn Connichiwa.on() and Connichiwa.onMessage() can now receive a space-seperated list of event names, which will register a callback for all of those events
	- Web developers can send their own messages and subscribe to them by either using Connichiwa.on(‘messageMessagename”) or Connichiwa.onMessage(“messageName”). An API for nicely sending custom messages is still missing.
- Messages from the websocket are now handled by the CWWebsocketMessageParser, which has been refactored into a common, master and remote part
	- master devices can now also receive append and loadscript messages
- Added Connichiwa.autoConnect. Once set to true, the first device that was launched will attempt to automatically connect to all other detected devices
	- For this, the launchDate has been added to the device info in the native layer and CWDevices
Introduced message-ack system and loadScript callbacks

- Every message now receives a random ID that makes it possible to identify that message
- Passing a received message to Connichiwa._sendAck() will now sent an acknowledgement message back to the sender
- When a “loadscript” message was received, an ack is now sent back after the script was loaded successfully
	- Connichiwa.loadScript() and CWDevice.loadScript() can now receive an optional callback function which is called when the ack for the loadScript message was received