Add --use-cluster-certificate flag to secure Che endpoints with cluster TLS certificate on Kubernetes

[mmorhun]

Signed-off-by: Mykola Morhun mmorhun@redhat.com

What does this PR do?

Adds flag --use-cluster-certificate to server:deploy command to use default ingress certificate for Che ingresses.

What issues does this PR fix or reference?

eclipse-che/che#18079
Depends on: eclipse-che/che-operator#508

How to test this PR?

The same way as eclipse-che/che-operator#508 but instead of CR patch use --use-cluster-certificate flag.

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[tolusha]

I am against adding more flags to server:deploy command since we are supporting --helm-patch-yaml and --che-operator-cr-patch-yaml flags.

For the time being we can deploy Eclipse Che without generating an untrusted SSL cert in the following way:

1. helm

cat >/tmp/che-cr-patch.yaml <<EOL
global:
  tls:
    secretName: ''
EOL

chectl server:deploy --installer helm ... --helm-patch-yaml /tmp/che-cr-patch.yaml

2. operator
```bash
cat >/tmp/che-cr-patch.yaml <<EOL
spec:
  k8s:
    tlsSecretName: ''
EOL

chectl server:deploy --installer operator ... --che-operator-cr-patch-yaml /tmp/che-cr-patch.yaml

Here is the issue to improve Eclipse Che deployment by specifying patch file content directly in the command line eclipse-che/che#18324