REFACTOR: Consistent naming for sensor identifiers

Previously I was using a mixture of sensor/device/remote naming, which
was unnecessary.  Refactored for readability.
Code clean-up while I consider a restructure

(Guess who's trying out ReSharper?)
Reordered params on BodyFrameReadyEventArgs constructor for consistency
Simplified KinectDataPublisher

I'd previously kept a StuffBodyBag method in case I wanted to plug in some
pre-processing at that stage, but it is not adding anything at this point.
Removing.

ProcessBodies did not need to be public.
New body priority field
Handling unlikely (but possible) case of null body list when processing
Improved code documentation
Encapsulating joint position in a struct to clean up code
Updating copyright information
Initial body processor implementation

Sample implementation of how to plug in classes that process body
information before it is sent down the wire and assign ambiguity flags and
other data.

Perhaps not the best name ever, but it sure sounds better than
"body plugin".
Sending an empty body list only once

If we don't send an empty body list the first time we are left with no
tracked bodies, chances are the client will keep the list of known bodies
cached as if it were still valid. We need to update it at least once with
an empty list. Tracking the last body count sent.
Merge branch 'release/0.1.4'