Add a datacenter resource.

[hdost]

The purpose of this is to allow for people running in a hybrid environment.

Relates #1409

Changes

Please provide a brief description of the changes here.

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

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]
• schema-next.yaml updated with changes to existing conventions.

[jsuereth]

We have tooling to autogenerate markdown, you should use <!-- semconv datacenter --> here for consistency.

See: https://github.com/open-telemetry/semantic-conventions/blob/main/model/README.md

[hdost]

🤔 I used the automated tool. I wonder if because the name was missing this resulted.

[hdost]

Well I found out what the issue was, perhaps I missed it in my reading of the various documentation, but I didn't see any mention that you need to first manually create a file which has the reference which you are mentioning, and then it will replace the contents between. I can understand the use, but it's not exactly clear as a first time user of the weaver tool.

[hdost]

@jsuereth am i missing something

[jsuereth]

This needs a name field, set it to datacenter for now

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[hdost]

This is a bit of an anti pattern ... stale because i haven't received a review?

Also check failure is unrelated to this change.

[joaopgrassi]

Not sure it is a good idea to use the abbreviation here. I'd be more inclined to go with "Data Center" instead.