[batonogov]

Update the DoQA chart from 0.7.2 to 0.8.0 for the vendor 4.3.4-box release. Pin backend to 4.3.3-box and frontend to 4.3.1-box exactly as published in configs_4_3_4.zip; remaining application image pins are unchanged.

Expose doqaBackendUrl (DOQA_BACKEND_URL) in values, the schema, and the shared environment ConfigMap. Pass it and the existing apiBaseUrl (API_BASE_URL) explicitly to the autotest-parser, which does not consume that ConfigMap. Both default to empty strings, matching vendor configuration. Regenerate the README and document the upgrade.

Validation:

• All commit hooks passed, including helm-docs, Helm lint, manifest rendering, and DoQA portability checks.
• Compared the full vendor archives for 4.3.2 and 4.3.4: no service removals/additions or nginx changes; Compose adds the parser backend URL and RabbitMQ comments.
• All application image pins match the new archive. The changed backend/frontend image configs have identical Env, Entrypoint, and Cmd contracts.
• Checked that default and explicit URL values reach both the ConfigMap and parser.

No live-cluster or application migration smoke test was performed.

Review completed against commit 3f5d479a773616fdcb3fcac7b160cb23ab600c18:

• PR CI passed; local ct lint also passed with chart version-increment validation.
• Compared old/new manifests in five scenarios: in-tree dependencies, external dependencies, explicit URLs, custom full name plus Telegram worker, and autoscaling/monitoring/network policies/PDBs. Resource identities, selectors, PVC specifications, secret key sets, RBAC and security contexts are unchanged. Differences are limited to release labels/checksums, the two image pins, and the intended URL additions.
• Every scenario rendered equivalently under Helm 3.16.4 (CI version) and Helm 4.3.1.
• Inspected URL handling in the actual parser source layer: absent and empty DOQA_BACKEND_URL both retain same-origin behavior; a nonempty internal URL preserves the request Host header.
• Helm 3 release packaging passed; CI inputs/local artifacts are excluded.

No confirmed defects found in this diff. Database migration behavior and application-level integration still require a live deployment; image metadata and render checks do not establish runtime correctness.