feat(helmsman): add isolated esignet-standalone-2.0.0 profile

[bhumi46]

Summary

Add a second, fully isolated Helmsman profile, esignet-standalone-2.0.0, that can be deployed side-by-side with the existing esignet-standalone profile in the same cluster without colliding.

Motivation

Testing/rolling out a new eSignet version currently requires either overwriting the existing esignet-standalone deployment or provisioning a whole new cluster. A namespaced-isolated profile lets both versions run concurrently for comparison/validation before cutting over.

Changes

• New Helmsman/dsf/esignet-standalone-2.0.0/ (esignet-dsf.yaml, testrigs-dsf.yaml, signup-dsf.yaml) — namespaces, Helm release names, and hostnames all suffixed -2-0-0 so they don't collide with the original profile's esignet-mock, esignet-mosipid1, esignet-mosipid2, esignet-sunbird, signup, kernel, mock-smtp, etc.
• New Helmsman/hooks/esignet-standalone-2.0.0/ — all hook scripts updated to match, plus isolated Postgres database names (mosip_esignet_2_0_0, mosip_kernel_2_0_0, etc.) and isolated captcha secrets in the shared captcha namespace.
• Helmsman/dsf/esignet-standalone/external-dsf.yaml — new databases.* entries added (pure additions) so the isolated profile gets its own databases in the same shared Postgres instance.
• .github/workflows/helmsman_esignet.yml, helmsman_testrigs.yml, helmsman_signup.yml — new esignet-standalone-2.0.0 profile option, and exact-match esignet-standalone conditionals refactored to prefix-matching so both profiles share the same standalone-specific logic.
• docs/ESIGNET_STANDALONE_DEPLOYMENT_GUIDE.md — short note on the new profile.

external-dsf.yaml/prereq-dsf.yaml (shared infra) and the Terraform profile stay untouched and shared between both profiles.

Known follow-up

The kernel services (authmanager, auditmanager, otpmanager) don't expose their DB connection config in the DSF/hook files — it appears to come from the Helm chart's own default values. The new mosip_kernel_2_0_0/mosip_audit_2_0_0/mosip_otp_2_0_0 databases are created, but nothing currently points those specific services at them; needs follow-up with visibility into the chart's values schema.

Sub-tasks

• test: validate esignet-standalone-2.0.0 core deployment (Go eSignet) #389 — Validate esignet-standalone-2.0.0 core deployment (Go eSignet)
• test: validate esignet-misp-onboarder against esignet-standalone-2.0.0 #390 — Validate esignet-misp-onboarder against esignet-standalone-2.0.0
• test: validate apitestrig suite against esignet-standalone-2.0.0 #391 — Validate apitestrig suite against esignet-standalone-2.0.0
• feat(helmsman): replace generic apitestrig/uitestrig charts with eSignet's own for esignet-standalone-2.0.0 #392 — Replace generic apitestrig/uitestrig charts with eSignet's own for esignet-standalone-2.0.0

[bhumi46]

PR raised: #303

[bhumi46]

Follow-up PR raised: #304 (fixes a postgres-init-esignet template failure hit after #303 merged)

[bhumi46]

Note: the keycloak-resource-copy fix wasn't included when #304 was merged (likely a timing race — it was pushed just before the merge). Raised as a separate PR: #305

[bhumi46]

Follow-up PR raised: #306 (reverts esignet-standalone-2.0.0's mock-smtp public hostname to the shared smtp.${domain_name}, since smtp-2-0-0 was never added to the terraform DNS list)

[bhumi46]

Raised PR #307 with the esignet-go-* rename for the esignet-standalone-2.0.0 profile (namespaces, release names, hostnames, base SoftHSM/captcha secrets, and the helmsman_esignet.yml softhsm-skip-releases restructuring).