parametric: avoid redefining otel SpanKind and StatusCode

[mabdinur]

Motivation

• Use the definitions of SpanKind and Status Code provided by the opentelemetry-api (link).

Changes

• Removes SpanKind and StatusCode enums from dd_constants
• Replaces all references to dd_constants.SpanKind and dd_constants.StatusCode with opentelemetry.trace.SpanKind and opentelemetry.trace.StatusCode.
• Updates all parametric apps to support the enum values returned by the python SpanKind enum (the main change here is that otel SpanKind values start at 0 instead of 1).

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team