Change protocol name to TLS in QuarkusRestClientBuilder

[sberyozkin]

This PR only changes SSL to TLS; I haven't verified if in fact on Java 11 SSL still defaults to TLSv1.2 but even if does it is better to have TLS to avoid various scanners reporting false positives.

I think having TLS is the most flexible option because (quoting some lines from Java Crypto docs):

• TLS 1.2 has been the default-enabled TLS protocol since Java 8
• TLS protocols provide a built-in mechanism to negotiate the specific protocol version to use. When a client connects to a server, it announces the highest version it can support

So if we explicitly start with TLS1.2 then it may fail against the legacy servers which only implement TLS 1.0 or just don't correctly implement TLS version negotiation.

With TLS Quarkus client will start with TLSv1.2 but will be able to drop to TLSv1.0 if necessary.

Also CC @cescoffier

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

🚫 This workflow run has been cancelled.

Failing Jobs - Building 957fbb4

Status	Name	Step	Failures	Logs	Raw logs
⌛	Initial JDK 11 Build		⚠️ Check →	Logs	Raw logs
⌛	Attach pull request number		⚠️ Check →	Logs	Raw logs
⌛	CI Sanity Check		⚠️ Check →	Logs	Raw logs

[gsmet]

This will have to wait. CI is overloaded right now, cancelling the build.

[sberyozkin]

No problems, it can wait