Issue 181 wear support

@barbeau This is getting quite large so I figure I'll take a break and get some feedback.

I would like to get an app on the wearable which has 2 use cases:
1.  Browses starred stops.
2.  View ArrivalInfo for a stop.

Designwise, I created a long running ```NodeService``` on the device which is the sole interface for the wearable to the Oba data.

The wearable fires messages to the ```NodeService``` to request data synchronization updates.

The NodeService will then update the Wearable datastores with the requested data updates via Wearable.DataApi calls.  The source of these data updates can be direct calls to the ObaApi or data from the ObaProvider, depending on the use case requirements.

For now I've only implemented the first use case of retrieving Starred Stops.

Implementing a polling ArrivalInfo hook into the NodeService would be next on my agenda.

I tried to document any areas I feel required extra inspection with todo tags.
>I agree that the play services should be abstracted out. I think I put it here because the base OBA-android module had a play services dependency already built in.

oba-android does have a dependency on play services.  We've had a number of requests for a pure open-source version of OBA Android, though, so hopefully we can work in a build variant for that in the future.

>Just wanted to note though that wearables require syncing with an Android device which has the Android Wear app, and the Android Wear app already has a hard dependency on Play Services.

Ok, good to know.