chore(deps): update dependency gitlab-org/caproni to v2.28.0

See merge request !679

chore(deps): update dependency https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git to v1.50.0

chore(deps): update dependency hashicorp/terraform to v1.15.3

See merge request !681

chore(deps): update dependency kubernetes/kubernetes to v1.36.1

See merge request !682

chore(deps): update dependency gitlab-org/caproni to v2.29.0

See merge request !683

chore(deps): update dependency helm/helm to v4.2.0

See merge request !684

chore(deps): update dependency https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git to v1.50.0

See merge request !685

chore(deps): update dependency metalbear-co/mirrord to v3.210.0

See merge request !686

chore(deps): update dependency ruby/ruby to v4

See merge request !548

chore(deps): update registry.gitlab.com/gitlab-com/gl-infra/common-ci-tasks/renovate docker tag to v4.2

chore(deps): update registry.gitlab.com/gitlab-com/gl-infra/common-ci-tasks/renovate docker tag to v4.2

See merge request !687

.releaserc.json was listed in _skip_if_exists, which meant copier
recreated the file on every update after a user deleted it. Projects
opting out of semantic-release had to ship a recurring delete commit
on each upgrade.

Removing the entry lets copier's three-way merge handle the file like
any other: deletions stick, template edits still propagate to projects
that kept the file, and real conflicts surface as inline markers
instead of being silently overridden. Three behaviours are pinned by
new tests under tests/, each running copier copy at v1.50.0 then
copier update against the ref under test.

The three existing semantic-release migration scripts already
early-exit when .releaserc.json is absent, so no migration changes are
needed.

chore(deps): update dependency gitlab-com/gl-infra/platform/runway/fairway to v1.19.0

See merge request !690

feat(template): respect user deletion of .releaserc.json on update

See merge request !689