Semconv generation improvements

[lmolkova]

Description

Prepares tooling to allow https://github.com/open-telemetry/opentelemetry-python/pull/3964:

• fixes namespace exclusion issue (that prevented os and net namespaces from being generated
• adds support for attribute exclusion
• enables mypy on semconv and fixes violations
• adds check for duplicate const definition (apparently there is no linter check for it)

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

• manually add duplicate attribute or metric, check if generation printed errors and script failed
• try excluding attribute check that it's not generated

Does This PR Require a Contrib Repo Change?

Answer the following question based on these examples of changes that would require a Contrib Repo Change:

• The OTel specification has changed which prompted this PR to update the method interfaces of opentelemetry-api/ or opentelemetry-sdk/

• The method interfaces of test/util have changed

• Scripts in scripts/ that were copied over to the Contrib repo have changed

• Configuration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in

  • pyproject.toml
  • isort.cfg
  • .flake8

• When a new .github/CODEOWNER is added

• Major changes to project information, such as in:

  • README.md
  • CONTRIBUTING.md

• [ ] Yes. - Link to PR:

• [ ] No.

Checklist:

• [x] Followed the style guidelines of this project
• [x] Changelogs have been updated
• [ ] Unit tests have been added
• [ ] Documentation has been updated

[xrmx]

@lmolkova please add a changelog entry, this is a good change to record

[lzchen]

I think mypy build is complaining on the deprecated decorators. Try passing the version="1.25.0" directly.

@deprecated(
    reason="Use :py:const:`opentelemetry.semconv._incubating.attributes.OsTypeValues` instead.",
    version="1.25.0",
)

[lmolkova]

version="1.25.0",

the problem is that we don't know when the attribute was deprecated. I can only provide the current version (1.25.0), but it'll be updated every time code is regenerated with new version and it won't be accurate.

We might add a property to track the version in the schema - https://github.com/open-telemetry/semantic-conventions/issues/1117 and then we'd be able to generate accurate docstring.

For the time being, I'd prefer to keep it empty and suppress the lint check.

Update: @deprecated(reason="...", version="...") still raises a warning 🤷‍♀️

[lzchen]

@lmolkova

I'm okay with ignoring the mypy warnings for deprecated.