Limit the maximum length of the value of kubernetes.cluster-id configuration option

Two Kubernetes Service will be created when a session cluster is deployed, one is the internal Service and the other is the rest Service, we set the internal Service name to the value of the kubernetes.cluster-id configuration option and then set the rest Service name to  ${kubernetes.cluster-id} with a suffix -rest appended, said if we set the kubernetes.cluster-id to session-test, then the internal Service name will be session-test and the rest Service name be session-test-rest; there is a constraint in Kubernetes that the Service name must be no more than 63 characters, for the current naming convention it leads to that the value of kubernetes.cluster-id should not be more than 58 characters, otherwise there are scenarios that the internal Service is created successfully then comes up with a ClusterDeploymentException when trying to create the rest Service.