feat: skip CI pipelines when updating main branch on release

When a new version of common-ci-tasks is released, the semantic releaser process will push a change to the main branch to update the documentation so that it always reflects the latest version.

Unfortunately, this leads to a chicken-and-egg situation where pipelines will fail.

This makes the project look like the pipeline for main is always broken, which is unfortunate.

This fixes that problem.