Add enum values to deployment.environment.name

[Arnav-Bansal]

Fixes #

Changes

This PR adds 4 enum values (Production, Staging, Test, Development) to deployment.environment.name attribute.

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)

[kamphaus]

Is it right to have stable values inside a development enum?
Should the values be development stability as well?