Insteon_IO: Add Initial Code for IO Library

Contributed by John Pellegrino <jpellegrino8@gmail.com>
Insteon_IOLinc: Change Library Name to IOLinc
Insteon_IOLinc: Modify Poll Sensor Status to Allow for Multiple Sensors
Insteon_IOLinc: Remove Unnecessary Variable from set_relay Subroutine
Insteon_IOLinc: Store Sensor Value as HEX not Decimal
Insteon_IOLinc: Add Perldoc Comments
Insteon_IOLinc: Add Ability to Store Multiple Sensor Values
Insteon_IOLinc: Add Ability to Retreive Sensor Data From Multiple Sensors
Insteon_IOLinc: Use $msg{extra} not $val in is_info_request
Merge branch 'master' into insteon_iolinc
Insteon_IOLinc: Set Awaiting Ack Flag for IO sensor_status Request
Insteon_Thermo_i2: Remove Complex Code Creating Child Objects

The code is just too difficult to try and make work.  Either the child objects have to be stored in a hash, which results in awful looking veriable names that are not user friendly to the basic user.

The removed code made user friendly variable names, but these variables could not be used in other user code because the init code was not eval'd until runtime.
Insteon_thermo_i2: Remove Parent_Event Routine

Not needed without tied children.
Insteon_thermo_i2: Change Name of Child Objects

While designed for i2 devices, the child objects should work with i1 devices as well, except the humidity object which I don't believe exits for i1 devices.
Insteon_thermo_it: Cleanup Example Thermostat Code File

Fix to match current code base
Insteon_thermo_i2: Add Example to Thermostat Code File for Child Objects

Add example entry into code file to demonstrate how to create child objects that are tied to parent item
Insteon_thermo_i2: Fix Comments in Example Code
Insteon_thermo_i2: Remove Complex Tie Example from Example User Code

Will add to individual child objects instead
Insteon_thermo_i2: Add Parent Event Routine to Base Thermostat Code

parent_event is called by tie_event on state changes in the parent.  The routine updates the child object with the correct state
Insteon_thermo_i2: Add Child Object to Parent Hash and Call Tie_Event

The child objects are stored in the parent hash so that the parent can locate the correct child to update it.

tie_events is set on child object creation.