feat: Adding candidate and relationship btw apm and kinesis stream

[vinaykonatala]

Relevant information

We are establishing a relationship between APM and AWS Kinesis Stream by using the ARN as the matching criterion. Users or customers from the APM service need to manually send the ARN within the cloud.resource_id span attribute.

On the Cloud Monitoring platform side, we are associating tags with the aws.Arn for AWS Kinesis streams, ensuring that the collector.name is equal to cloudwatch-metric-streams.

The ARN is formatted as follows for a function: arn:${realm}:kinesis:${region}:${accountId}:stream/${StreamName}

Checklist

• I've read the guidelines and understand the acceptance criteria.
• The value of the attribute marked as identifier will be unique and valid.
• I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

[CLAassistant]

All committers have signed the CLA.