Geolocation context sends values as doubles/floats

- We had to change the geoLocation map to <String, Object> to accept the
  values without toString-ing them.
- Fixes #17
Unfinished play-services fix
Grabs the advertising Id on a background thread

- Play Services can't run on the main UI thread, so we get the
  advertising Id on a background thread and then add it to the Subject.
  If an event is sent right after a Subject is created, there is a high
  chance the advertising Id won't be added for that initial event.
  Once the Id is received, it will be added to the following events
  sent.
- This is not a complete fix for the Play Services branch. One more fix
  needs to go in to detect if the Play Services is made available.
- Ref: #16
Removed SLF4J logging

- We have the Android logger which is native and better.
- Fixes #19
Follow up fix for Play Services fix

- Using Reflection to get the advertising ID
- Fixes #16
- Goes with d974c4f297fa150760312b3431b194702f92247e
Merge branch 'feature/play-services' into develop
Removing super.flushBuffer

- We're affected by a bug in the tracker-core by calling super.
- Since we don't rely on super.flushBuffer, we can remove it.
- Fixes #20
Updating tracker-core to 0.1.3

- Fixes #22
- This will break the build until core 0.1.3 is published.
Fixed bug with pending events not being updated

- Pending events are not properly unset if flushBuffer is called before
  the AsyncTask returns. We clear the indexArray of pending tasks, and
  eventually "forget" to unset the pending flag.
- Fixes #24
Removing pom hack

- Fixes #15
Added in 0.1.1 entries
Merge branch 'develop'

Conflicts:
	CHANGELOG