feat: automated releases and auto labelling

[jmeridth]

Part of github/github-ospo#78

Pull Request

Proposed Changes

• lint pr title adhering to conventional commits (helps with auto labelling)
  • Update CONTRIBUTING.md
    • automated releases
    • how to file a bug report
    • how to file an enhancement
  • Update pull_request_template with new standard
• setup autolabelling through release-drafter github action config
• create auto-labeler workflow
• change release-drafter workflow to release
  • create release, including new tag
  • create discussion announcement based on release
  • build container images, tag them and release them

Manual Actions:

• create revert and maintenance labels
• put repository and category IDs into secrets for the discussion create action

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• run make lint and fix any issues that you have introduced
• run make test and ensure you have test coverage for the lines you are introducing

Reviewer

• Label as either bug, documentation, enhancement, infrastructure, or breaking

[zkoppert]

I think these releases may silently fail on major version changes since we aren't updating action.yaml files. That sound right to you? We can make that a future pr (set of prs) if desired.

[jmeridth]

I think these releases may silently fail on major version changes since we aren't updating action.yaml files. That sound right to you? We can make that a future pr (set of prs) if desired.

yes, currently, we, as the PR reviewers, need to confirm the action.yml was updated if we're going to flag a PR with the breaking label. We can automate that though. Definitely a new PR. I'm a fan of https://github.com/tj-actions/changed-files for checking if a file is in the change set.

Do you think this work is a major version bump? I haven't been doing that. 😬

[zkoppert]

No major bump needed for this one, just looking to the future.