Update URL destination for Agent Operator CRDs

[clayton-cornell]

PR Description

This PR updates the documented URL for the Agent Operator CRDs

Which issue(s) this PR fixes

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[rfratto]

Sorry, not sure how I missed this one

[jdbaldry]

Some other instances:

pkg/operator/operator_test.go
156  	crdPaths, err := filepath.Glob("../../production/operator/crds/*.yaml")

docs/sources/operator/helm-getting-started.md
30   In this section, you'll install the [grafana-agent-operator Helm chart](https://github.com/grafana/helm-charts/tree/main/charts/agent-operator) into your Kubernetes cluster. This will install the latest version of Agent Operator and its [Custom Resource Definitions](https://github.com/grafana/agent/tree/main/production/operator/crds) (CRDs). The chart configures Operator to maintain a Service that lets  ... (truncated)

docs/sources/operator/deploy-agent-operator-resources.md
148      - Sets a `cluster: cloud` label for all metrics shipped to your Prometheus-compatible endpoint. Change this label to your cluster name. To search for `MetricsInstances` or `LogsInstances` in a *different* namespace, use the `instanceNamespaceSelector` field. To learn more about this field, see the `GrafanaAgent` [CRD specification](https://github.com/grafana/agent/blob/main/production/op ... (truncated)
406      This example tails container logs for all Pods in the `default` namespace. You can restrict the set of matched Pods by using the `matchLabels` selector. You can also set additional `pipelineStages` and create `relabelings` to add or modify log line labels. To learn more about the `PodLogs` specification and available resource fields, see the [PodLogs CRD](https://github.com/grafana/agent/blob/main�[0m�[1 ... (truncated)

docs/sources/static/set-up/install/_index.md
41   For more information, refer to the [Tanka](https://tanka.dev) configurations in the Grafana Agent [production](https://github.com/grafana/agent/tree/main/production/tanka/grafana-agent) directory on GitHub.

cmd/grafana-agent-operator/DEVELOPERS.md
77   folder](../../production/operator/crds). Deploy them from the root of the

[clayton-cornell]

I'll grab those in another PR

[jdbaldry]

I've not checked if all are relevant, I just searched for /production/ across the branch

[grafanabot]

The backport to release-v0.37 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-6241-to-release-v0.37 origin/release-v0.37
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bc91e84a7c4a7fcd9dffb04a6650a04284691968
# Push it to GitHub
git push --set-upstream origin backport-6241-to-release-v0.37
git switch main
# Remove the local backport branch
git branch -D backport-6241-to-release-v0.37

Then, create a pull request where the base branch is release-v0.37 and the compare/head branch is backport-6241-to-release-v0.37.