Publish eval2otel-python to PyPI

[haasonsaas]

Summary

PR #43 and PR #44 added the Python SDK preview, optional OTLP emission, provider auto-instrumentation hooks, an entry point, and optional Pydantic validation. The remaining release task from #2 is to publish the Python package as its own PyPI artifact.

What to do

• Decide the package name and ownership for on PyPI.
• Configure PyPI trusted publishing or a scoped API token for this repository.
• Add a release workflow that builds into sdist/wheel artifacts and publishes them on GitHub release.
• Add a release smoke that installs from PyPI and imports , , and .

Acceptance criteria

• A GitHub release publishes the npm package and the Python package without manual local steps.
• works from a clean environment.
• The installed package exposes the entry point named .
• The release docs explain npm vs PyPI versioning expectations.

Split from #2 after the SDK implementation landed in #43 and #44.

[haasonsaas]

Closing as a duplicate of #46. This first copy was created with shell-stripped inline code in the body; #46 has the correct release checklist.