Instructions for secrets are incorrect

Describe the bug

In the documentation the section on manually creating secrets has an error.

For secrets like OIDC, postgres, (the ones I tested) you are instructed to create a secret [release-name]-concourse. However, at install time the Deploy resource expects secret keys in [release-name]-web. E.g. postgresql-user, oidc-client-id, etc.

Reproduction steps

Create a secret my-release-concourse with fields postgresql-user and postgresql-password and install the release configuring to BYO your own postgres. You will see that the deployment pod and init container give an error that they could not find the secret.

Expected behavior

Either the documentation should be updated, or the templates should reflect the documentation. Either way is fine for me.

It would probably even be better to be able to configure the names of the secrets for the various inputs. As its pretty confusing to get this right anyhow and you have to jump through hoops to get them with the right name.

Additional context

No response

Start by locating the documentation section for manually creating secrets and the Helm templates that reference the release-specific secret names. Compare the documented [release-name]-concourse name with the [release-name]-web name used by the Deploy resource; done means the instructions and chart behavior agree, or the supported configuration is clearly documented.