Stabilize deployment environment

[Arnav-Bansal]

Changes

This PR introduce changes to stabilize the deployment.environment.name field.

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[jsuereth]

This needs a changelog and rebase

[lmolkova]

We need to specify the role of attributes on the entity - see https://github.com/open-telemetry/semantic-conventions/pull/3339/changes#r2743336364

[thompson-tomo]

The key thing which was missed is that the actual stability of the entity wasn't updated but rather just the stability in the doc was changed. This is why the policy passed.

approved by mistake

[lmolkova]

Should it be descriptive? As a result deployment entity does not have any identity attributes.

/cc @open-telemetry/semconv-service-and-deployment-approvers

[Arnav-Bansal]

Done. Added deployment.name as idenitify attribute as well.

[lmolkova]

Also, is this right that this entity is called deployment and not deployment.environment?

If it's deployment, should it contain any other existing deployment attrs such as deployment.name | id

[thompson-tomo]

Agree it makes more sense to me to have deployment & deployment.environment entities.

[Arnav-Bansal]

Updated the file to make it more apt.

[joaopgrassi]

We can't stabilize this, until we have decided on how to deal with the values of it: #2910.