docs: fix cm typo in google docs

[bjorn-stange-expel]

The configmap set up by the installer is argocd-cm not argo-cm, so I assume this is a typo?

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

[codecov]

Codecov Report

Merging #9577 (ba164ef) into master (7ca8c11) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9577   +/-   ##
=======================================
  Coverage   45.79%   45.79%           
=======================================
  Files         222      222           
  Lines       26377    26377           
=======================================
  Hits        12079    12079           
  Misses      12650    12650           
  Partials     1648     1648           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ca8c11...ba164ef. Read the comment docs.

[crenshaw-dev]

lgtm, thanks!

[crenshaw-dev]

Cherry-picked onto 2.4.