Change information about TLS support for the query service

[jpkrohling]

In the page linked below, we state that TLS support for the query service is non-existing. For 1.22, we need to state that this is supported if all the pieces of the work done by @rjs211 are merged by then.

https://www.jaegertracing.io/docs/1.21/security/#browser-to-ui

[yurishkuro]

This was already done in 3e3f229

[tillig]

It appears the text on that change didn't get fixed - the green check says it's available, but the text still says "no TLS/authentication" next to it, which is super confusing.

[yurishkuro]

@tillig good catch. I think TLS is "yes", but the authentication is still No, right?

Would you like to submit a patch to the docs?

[tillig]

I'm fine to submit that, sure. I don't actually know the answer to which is yes/no, which is why I started looking through the docs and that's how I got here. But I'll submit a patch based on your note above.

[tillig]

Looks like consumer-to-query gRPC supports TLS with cert authentication but HTTP only has TLS with no authentication.