Backend dependencies granularity for NoSQL and Messaging

[AlexanderWert]

Description

Similar to #621, we need to improve the granularity of backend dependencies that are NoSQL-based or messaging-based.

This, in particular, means that service.target.type, service.target.name need to be set properly and also the old field destination.service.resource needs to be updated accordingly.

The detailed changes are described in these spec changes:

• Spec: services dependencies granularity NoSQL #654
• Spec: services dependencies granularity Messaging #655

Summary of changes

DBs

• For Cassandra, define db.instance to the Keyspace name (if available)
• For MongoDB, define db.instance to the Database name (if available)
• For Elasticsearch, define db.instance as the Cluster name (if available, with heuristic).
• For Redis do not set the db.instance / service.target.name fields
• For Memcached do not set the db.instance / service.target.name fields
• For any other NoSQL database / store follow the spec

Messaging

• For azurequeue : use queue name
• For azureservicebus : use queue name or topic name
• Other: use already captured queue name

Agent Issues

• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-java#2711
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-dotnet#1754
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-nodejs#2822
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-python#1586
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-go#1267
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-php#728
• [META 659] Backend dependencies granularity for NoSQL and Messaging apm-agent-ruby#1290