Binding for MiOS (Vera) Automation controllers

This binding exposes read, and read-command, access to Devices controlled by a MiOS Home Automation controller, such as those seen at http://getvera.com.

It exposes the ability to do the following things in the MiOS HA Controller
* `Devices` - Read State Variables & Device Attributes, and invoke (single parameter) UPnP Commands to control the Device.
* `Scenes` - Read the current execution state of a Scene, and invoke those Scenes within the remote HA Controller
* `System` - Read System-level Attributes.

It uses the _remote control_ interfaces (aka "UI Simple" JSON Calls, and HTTP Long-polling) of the MiOS HA Controller to keep the _bound_ openHAB Items in sync with their counterparts in the MiOS HA Controller.

The "guts" is outlined in the root-level `README.md` file, along with the JavaDoc that's in the code (although, the `README.md` is better).  

The binding uses the openHAB _Transformation Service_ extensively to "map" the Data & Commands between the two systems.  I provide a set of example MAP transform files in the `examples/transform` directory of the Binding, but these can readily be augmented without needing to tweak the code.

Original code was used from the XBMC Binding, and then heavily modified.  Snippets included from the HTTP Binding for the various datatype mapping functions.

Submitting for early feedback, there will probably be a lot since it's my first binding  ;)
A few observations...

 1. The `unit:` prefix is redundant as all bindings will require a unit
 1. `<miosThing>` has multiple sub-patterns adding complexity to the overall binding config
  - `device:<deviceId>/service/<serviceURN>/<serviceVariable>` 
  - `scene:<deviceId>/<attributeName>`
  - `system:/<attributeName>`
 1. The `in:` and `out:` transformations should be omitted (read my comments in the Transformations section below)

An alternative binding config could be:

`mios="<unitName>:<deviceId>[:<param>=<value>[,<param>=<value>]...]"`

This has proven to be quite flexible using the `<param>=<value>` arguments since the key prefixes (`unit:`, `device:` and  `command:`) are not hard-coded in the binding config but parsed dynamically. 

For example, the following configs are semantically equivalent:

`mios="unit:<unitName>,device:<deviceId>/service/<serviceURN>/<serviceVariable>"`
`mios="<unitName>:<deviceId>:service=<serviceURN>,variable=<serviceVariable>`