Docs should cover how to respond to `Manifest generation error (cached)`

[jsoref]

Checklist:

• [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [x] I've included steps to reproduce the bug.
• [x] I've pasted the output of argocd version.

Describe the bug

Manifest generation error (cached) doesn't lead to users being able to fix the error.

To Reproduce

1. Migrate from argo-helm argo-cd 5.6.8 (with a old style CMP) to argo-cd 5.7.0 (without properly configuring a replacement CMP)
2. Try to get the CMP to work by setting up a CMP for conf

Expected behavior

• When there's an error about manifest generation (cached), there should be enough information somewhere to explain how to flush the cache (this could be in the form of Documentation, the FAQ, or in the GUI, or probably all of the above).

Screenshots

Version

{
    "Version": "v2.4.11+3d9e9f2",
    "BuildDate": "2022-08-22T09:13:16Z",
    "GitCommit": "3d9e9f2f95b7801b90377ecfc4073e5f0f07205b",
    "GitTreeState": "clean",
    "GoVersion": "go1.18.5",
    "Compiler": "gc",
    "Platform": "linux/amd64",
    "KustomizeVersion": "v4.4.1 2021-11-11T23:36:27Z",
    "HelmVersion": "v3.8.1+g5cb9af4",
    "KubectlVersion": "v0.23.1",
    "JsonnetVersion": "v0.18.0"
}

Logs

Paste any relevant application logs here.