Fix OTel Bridge span destination resource pseudo-code

[trentm]

This updates the pseudo-code for compatibility mapping of span
destination resource from OTel attributes to pass the
otel_bridge.feature gherkin tests. It more closely matches the current
Java APM agent implementation.

checklist

• Create PR as draft
• Approval by at least one other agent
• Mark as Ready for Review (automatically requests reviews from all agents and PM via CODEOWNERS)
  • Remove PM from reviewers if impact on product is negligible
  • Remove agents from reviewers if the change is not relevant for them
• Merge after 2 business days passed without objections
  To auto-merge the PR, add /schedule YYYY-MM-DD to the PR description.

/schedule 2022-05-07

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-05-06T04:59:00.371+0000

• Duration: 3 min 42 sec

[SylvainJuge]

Thanks for catching & fixing this @trentm !

[trentm]

@gregkalapos I haven't looked at the .NET OTel Bridge implementation (elastic/apm-agent-dotnet#1498). Do you know if it would need to update for this pseudo-code change?

[SylvainJuge]

@gregkalapos I haven't looked at the .NET OTel Bridge implementation (elastic/apm-agent-dotnet#1498). Do you know if it would need to update for this pseudo-code change?

I think that the dotnet implementation relies on gherkin specs, so if the spec tests are applied it should already be OK.