Add support for materialized-ops workflow

[BojanOro]

Adds support for writing git commits to materialized-ops during its code deployment pipeline.

Re: https://github.com/getsentry/devinfra-deployment-service/pull/907

[linear-code]

PRODENG-1716

[sentry]

Bug: The materialized-ops-set-image command runs unconditionally in a shared script, causing it to execute during canary deployments, which may be unintended.
_{Severity: MEDIUM}

Suggested Fix

Add conditional logic to deploy.sh to ensure materialized-ops-set-image only executes during the primary deployment. This can be done by checking an environment variable that distinguishes between canary and primary stages before invoking the command.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: gocd/templates/bash/deploy.sh#L12-L16

Potential issue: The `deploy.sh` script is shared between `deploy-canary` and
`deploy-primary` stages. The newly added `materialized-ops-set-image` command runs
unconditionally in both. This causes it to execute during canary deployments with a
canary-specific `LABEL_SELECTOR` (`'service=chartcuterie,env=canary'`), which may be
unintended. The expected behavior is often for such tracking commands to run only during
the primary deployment. This could lead to incorrect or duplicate deployment records in
the `materialized-ops` system, potentially complicating deployment monitoring and
rollbacks.

_{Did we get this right? 👍 / 👎 to inform future reviews.}