RFC: Add support for conventional commits and semantic release

[reece]

• https://www.conventionalcommits.org/en/v1.0.0/#summary
• https://github.com/semantic-release/semantic-release

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.

[reece]

This issue was closed by stalebot. It has been reopened to give more time for community review. See biocommons coding guidelines for stale issue and pull request policies. This resurrection is expected to be a onos.environ["GITHUB_TOKEN"]e-time event.

[jsstevenson]

@holtgrewe had sketched a release-please based implementation here

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[jsstevenson]

One wrinkle: in semantic-release, you designate breaking changes by including BREAKING CHANGE: in the commit body (whereas strictly speaking the conventional commits spec allows either this or a ! in the commit prefix to designate a breaking change). I kind of like this as a practice -- it forces the committer to spell out the breaking change in detail -- but we (Wagner lab) have just been doing the ! prefix, so it'd entail a slight change in workflow. More here