Add new attribute mappings

[stevejgordon]

Adds support for new attributes defined in more recent semantic conversion schema versions. This initial set is needed to support attributes emitted by the .NET Elasticsearch client instrumentation, which conforms to https://opentelemetry.io/schemas/1.21.0. The go.opentelemetry.io/collector/semconv/v1.5.0 package does not include these attributes, and the latest version only includes up to 1.18.0. For now, I've included the new attributes directly in our mapping code and updated them to ensure both old and new attribute names are supported. In the long term, we need to discuss how we handle other new attributes and have a strategy for mapping new schema versions as they are made stable and released.

[stevejgordon]

Thanks for the approval, @kruskall. I rebased this so that the commit was signed. What's the process for getting this merged?

[kruskall]

@stevejgordon 👋

There's no specific process, once the PR is merged the dependency in apm-server will be bumped and the changes included in the next release.
Code looks code but I'd like another pair of eyes to approve this to make sure this is the direction we want to go as we haven't decided on how to deal with different versions of otel semconv (#116)

removing approval to avoid merging this by mistake

[axw]

@stevejgordon I think the changes for TranslateSpan are fine, but there's a couple of issues in TranslateTransaction. Can you please check those? The server.* fields are mentioned in the 1.21 schema here: https://github.com/open-telemetry/semantic-conventions/blob/4bbb8c907402caa90bc077214e8a2c78807c1ab9/schemas/1.21.0#L15-L19

Adding attributes for a newer semver version is fine as long as we keep support for the older version. Longer term we need to figure out something sustainable, but we don't need to solve that today.

[axw]

@stevejgordon thanks, LGTM - just one minor comment.