Auto-infer destination.service.resource and adapt public API

[AlexanderWert]

#436 defines an update on the SPEC for destination fields.
APM agents need to comply with these changes, which includes the following:

• Infer destination.service.resource based on other fields
• Add a public API to set destination.service.resource
• As destination.service.name and destination.service.type are not used anywhere in the product, I propose to deprecate and remove them also in the public API (if already added there)
• Add a public API to start an exit span. This auto-infers the destination.service.resource based on the subtype if not set otherwise. Avoids creating nested exit spans and makes the service map work with those custom spans by default, without having to set any destination fields.

Spec issue

• [META 448] Auto-infer destination.service.resource, add public API, deprecate other destination.service fields #436

Agent issues

• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-java#1848
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-dotnet#1330
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-go#976
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-php#426
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-ruby#1022
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-nodejs#2103
• [META 448] Auto-infer destination.service.resource and adapt public API apm-agent-python#1159