First very very broad native DeviceManager implementation

- We have a native device manager that keeps track of our devices
- We are able to pass our ibeacon list to that manager and it will figure out which devices changed and send events to the delegate accordingly

There are still several problems with this, some of which are:
- CWDevice stores data that is not sent to the weblib, leading to messy code
- code duplication with the weblib
- having a delegate on a singleton (like in CWDelegateManager) makes no sense - switch to NSNotificationCenter? or get rid of singleton pattern?
- when sending data to the weblib, we cannot know which properties changed, so we have to sent the entire device every time - should we send the change event from the CWDevice? or return a list of properties that changed?
Removed native DeviceManager

Great, job, eh? Seriously, I thought long and hard about how to implement this nicely, and the nativemanager just didn’t seem to be the way to go. It didn’t add anything useful and caused code duplications and weird communication in the native app.
Therefore, the functionality of the devicemanager has now directly been incorporated into the BeaconMonitor. It keeps track of new and changed beacons and sends messages to the delegate accordingly, which sends messages to the weblibrary.
Furthermore, the singleton status of most classes was revoked - singletons and delegates don’t go well together, and I didn’t want to have to use NSNotificationCenter, as it can be easily misused to code dirty.
The weblibrary picks up the new messages, but its not completely implemented yet.
Furthermore, I tried to change some minor things to make stuff more clear, for example we don’t send a local device anymore but just a local id.
Also, we keep everything related to CoreLoacation in the beacon classes. CWWebApplication, CWWebserver and others should not be concerned with CoreLocation.
Web Library now handles the new events - we can now be notified of new, changed and lost beacons in the web app.

Furthermore, rewrote the CWNativeCommunicationParser of the web library.
Also, we now treat beacons with “unknown” proximity as lost, so beacons that are shut down or get out of range are detected faster.
Minor adjustments to design and events - we now nicely show nearby beacons
NO ISSUES | Issue Resolvement

- Commented Objective-C code
- Commented entire Web Library
- Updates JSCS config so it allows trailing whitespaces - we need that for markdown JSDoc comments
- Introduces new JSDoc config that allows us to use markdown and updated JSDoc bash script so it uses the config
- Updated both native and weblib documentation to the new comments
NO ISSUES | Issue Resolvement

- Commented Objective-C code
- Commented entire Web Library
- Updates JSCS config so it allows trailing whitespaces - we need that for markdown JSDoc comments
- Introduces new JSDoc config that allows us to use markdown and updated JSDoc bash script so it uses the config
- Updated both native and weblib documentation to the new comments
Merging commit