Update sensitive information placeholders in documentation and config…

[kirkryan]

This pull request standardizes the use of placeholder values for sensitive credentials and secrets across documentation and configuration files. Instead of using real or example passwords, API keys, and secrets, the documentation now consistently uses clearly marked placeholders (e.g., YOUR_PASSWORD_HERE, YOUR_CLIENT_ID_HERE). This change improves security practices and helps prevent accidental use of insecure example secrets in production environments.

The most important changes are:

Credential and Secret Placeholders in Documentation:

• Replaced hardcoded or example passwords, API keys, client IDs, and secrets with placeholders in all relevant API, configuration, and environment variable examples throughout the documentation (e.g., YOUR_PASSWORD_HERE, YOUR_CLIENT_ID_HERE, YOUR_DB_PASSWORD_HERE). [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23]

Configuration and Deployment Example Updates:

• Updated all example configuration files (values.yaml, .env, README.md, and Kubernetes/Helm manifests) to use the new placeholders instead of insecure default values. [1] [2] [3] [4] [5] [6] [7] [8] [9]

These changes make it clear to users that they must provide their own secure values and help prevent accidental exposure of sensitive information.