allow preventing test hooks from being rendered (again)

Problem: We are using GCP Cloud Deploy to deploy the chart as a dependency to a GKE cluster. Cloud Deploy calls skaffold render, which, in our case, uses Helm to render the manifest. The rendered manifest then gets applied, including the test-db-interaction deployment. Although the test runs successfully and is marked as completed/successful, Cloud Deploy still marks the release as failed since the test pod is not marked as ready.

Potential Suggested Solution: Introduce a conditional render around the test deployment.

Why did I create a new issue? This is essentially the same request as described in issue #77 . That issue was marked as resolved because the test passed, and the deployment tool no longer flagged the release as failed. However, the underlying problem of preventing the test deployment from being rendered still persists.

I'm happy to create a PR for the suggested solution myself—just wanted to confirm that this mechanism would be an acceptable approach before proceeding.

Inspect the Helm templates that define the test-db-interaction deployment and start with the chart render path used by skaffold render. Confirm that a conditional option can omit this deployment from the rendered manifest while preserving the existing test behavior.