[Feature] Lets choose StatefulSet as an installation option

[livelace]

Right now we have only the "Deployment" type for Trino installation. Problems with such an approach:

1. Random suffixes in Pod's names are not very suitable for human eyes, especially when you are trying to investigate where the problem is. StatefulSet Pods have incremented suffixes and look much better.
2. The main problem. StatefulSet pods have Stable Network ID and thus predictable FQDNs. With predictable FQDNs you can generate corresponding Certificates with proper SANs. And as a consequence - you can setup internal communications over HTTPS without any problems.

[talpa-robin]

I have a third problem / use-case that we just ran into: If you want to use caching and add a PVC to a Pod. You'd need a StatefulSet to map specific pods of a StatefulSet (pod-0, pod-1, pod-2 etc) to specific PVCs (pvc-0, pvc-1, pvc-2 etc). If the pod itself doesn't know which index it has (as it is with Deployments etc) how would it know the name of the PVC it needs to attach?