Setting up to deploy snapshots from travis-ci
Changed spanId's to be 32bit not 64bit.
Changes for consistency with ruby telemetry-tracer gem.

- Logging output now uses snakecase names for compatibility ruby
telemetry-tracer.
- Span.id property is now Span.spanId
- Span.parentId property is now Span.parentSpanId
- Span.startTimeNanos is now Span.startTime
- Annotation.startTimeNanos is now Annotation.loggedAt
- Trace.id is now Trace.traceId
Removing telemetry-service and telemetry-service-sink

These may come back in future but for now we want to concentrate on
capturing the data in a format compatible with the telemetry-tracer gem
output.
Removing AnnotationNames.FALLBACK_SERVICE_NAME

This was being set in the HttpClient based on the hostname which is
already present in the span name.  The only real usage was within the
telemetry-service network view which has been removed for now.
Added host and pid to spans.

This uses the ManagementFactory.getRuntimeMXBean().getName() which
returns a name of the form 'pid@host' which we parse at startup to avoid
continual invocation costs.
Rename maven-deploy-settings.xml correctly for travis-ci.
Updating username/password pair for push of snapshot
Merge pull request #3 from leapingfrogs/output-consistency

Output consistency

Making a number of minor changes to make the output format of the telemetry java agent more closely compatible with the output of the ruby telemetry-tracer.

This also includes removal of the telemetry-service and telemetry-service-sink as we currently aren't using it and would like to focus on the collection initially.