When Tekton Results is disabled, the in-cluster Postgres DB persists and must be manually deleted

This is because the postgres stateful set does not configure any specific PVC retention policy.

If this is expected behavior the docs will need to be updated to include this as a manual step when disabling Results. If this is unexpected behavior, Results should set an appropriate persistentVolumeClaimRetentionPolicy on the postgres stateful set.

NOTE: the persistentVolumeClaimRetentionPolicy is only enabled by default as of Kubernetes 1.27 (OCP 4.14). If we need to support any OCP versions prior to 4.14 we'll need to ensure this setting is not present.

Workaround: Manually deleting the pod

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

 # <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *