Revisit release process

[jack-berg]

The current release process seems out of order and requires maintainers to run commands locally with a personal access token.

Out of order

Updating the changelog comes after cutting the release.

The PR to update the changelog is a good opportunity to double check the contents of the release, and review how each change is framed for consumers. I think we should make sure we do this prior to tagging the release.

Requires maintainers to run commands locally

See steps here:

https://github.com/open-telemetry/opentelemetry-configuration/blame/16452629a3f119af3d1fa74a17c9f85ad5076119/RELEASING.md#L26-L46

Proposal

Follow the release process from opentelemetry-proto: https://github.com/open-telemetry/opentelemetry-proto/blob/main/RELEASING.md

• This includes a PR to update CHANGELOG.md as the first step in the process
• The rest of the process is managed in the Github releases workflow, which
  • Input a tag that will be created on publish
  • Click a button to generate release notes from CHANGELOG.md
  • Publish a tag and the release anouncement in a single step
  • No local commands required

[jack-berg]

Noticed these issues when considering this comment: #146 (review)

Maybe it's easy enough to label the title of this PR breaking: refactor OTLP exporter so that at release time these are listed in the release notes