Add first class support for TLS in tunnel server

[Yshayy]

At present, Preevy tunnel only forwards HTTP traffic, and HTTPS is handled by an external service that performs TLS termination. The tunnel server uses the HTTP host header to route traffic to the appropriate service.

If TLS support is added to the tunnel server, Preevy will be able to route non-HTTP traffic to the correct host using Server Name Indication (SNI). Specific protocol manipulation, such as rewriting headers, can be accomplished by explicitly specifying the channel type or using Application-Layer Protocol Negotiation (ALPN).

This new feature will enable users to directly connect to their non-HTTP services, such as databases, provided that their client supports TLS and uses SNI.