Add config to provide git push options

[MatthewJohn]

I've created this change for myself (currently in testing) and created the PR to see if you believe it would be useful.

The rational behind this:

• I use Gitlab primarily but replicate to Github.
• Some projects use both Gitlab CI/CD and Github actions (mainly for testing/tagging etc. in Gitlab and then producing artifacts in Github).

When I merge into Gitlab, semantic release runs on main and performs the release. The release commit, by default, uses [skip ci], which is appropriate for Gitlab. Unfortunately, when the release commit is replicated to Github, it also respects this and skips Github actions.

This change means that I change the commit message, removing [skip ci] and use a git push option ci.skip (see https://docs.gitlab.com/ee/user/project/push_options.html), which will only skip the CI/CD pipeline in Gitlab.

I'm creating this PR to get feedback if it's a feature that you believe would be useful and, if so, I can tidy it up after testing, add tests etc. ready for proper review :)

Many thanks
Matt

[Luckymhe]

How can I update branch. Master branch suddenly stop working