feat(chart): add relay.deploymentAnnotations for Reloader support

[torstenrudolf]

What

Adds a relay.deploymentAnnotations values knob (default {}) to the Buzz relay chart, rendered onto the relay Deployment's own metadata.annotations. Bumps the chart to 0.1.4.

Why

The chart only exposed pod-template annotations (relay.podAnnotations). Stakater Reloader reads its trigger annotations (secret.reloader.stakater.com/reload, reloader.stakater.com/auto) from the Deployment's metadata.annotations, not the pod template — so there was no way to opt a deployment into auto-rolling when a Secret changes.

This matters when DB/Redis credentials come from a Secret injected as pod env vars: env vars are read once at process start, so if the backing Secret is later updated (e.g. a credential rotation), running pods keep the stale value and can fail auth until they are manually rolled. The chart's existing checksum/secret pod annotation only tracks the chart-managed Secret, so it doesn't cover externally-managed Secrets.

With this knob a consumer can set:

relay:
  deploymentAnnotations:
    secret.reloader.stakater.com/reload: <secret-name>

and Reloader will auto-roll the pods when that Secret changes (requires the Reloader controller running in-cluster).

Rendered output

kind: Deployment
metadata:
  name: t-buzz
  labels:
    ...
  annotations:
    secret.reloader.stakater.com/reload: <secret-name>
spec:
  ...

Default (unset) renders no annotations block — no behavior change for existing consumers.

Testing

• helm lint clean.
• helm template verified both cases: default emits no Deployment-level annotations; with the value set, the annotation lands at Deployment.metadata.annotations (where Reloader reads it), not the pod template.

Follow-ups (downstream, not in this PR)

• Publish 0.1.4 to the OCI chart repo, then bump the dep + set the annotation in consumer values.
• Requires the Reloader controller to be installed in the target cluster for the annotation to take effect.