Fix protobuf CI publish jobs

Part of #3 (closed)

See: #3 (comment 806532)

Attempts to fix:

• The protobuf:publish:python:gitlab job is not running
• The python:publish-to-gitlab is running where it shouldn't

And a workaround for:

• In the GitLab release, the version number of the message schemas python library does not match the version number of the release

By switching to the release-it merge request flow.

assigned to @st981

I am not sure why, and this is untested, but this is different than what we have for the OpenAPI generator template. So I matched it to what we have there.

changed the description

mentioned in issue #3 (closed)

added 1 commit

• 6975eba9 - ci: use release-it merge request flow

Compare with previous version

changed the description

requested review from @mk2155

approved this merge request

enabled an automatic merge when all merge checks for 6975eba9 pass

merged

mentioned in commit a0c9f1eb