Support TLS 1.3

[evolutionise]

Background

We want to support TLS 1.3 for server/tentacle communication.

• Shortcut story
• TLS1.3 Tentacle Server Comms - current state
• Testing journal

We currently explicitly specify supported SSL protocols in Halibut, Tentacle, and Server.

In the long term, we intend to explore following Microsoft recommendations and not configuring protocols explicitly and leaving the choice to the OS.

In the immediate term, we are just going to add TLS 1.3. to the configured set of supported protocols.

This PR will be followed by PRs to Tentacle and Server to update Halibut.

Results

This PR just adds SslProtocol.TLS13 to the set of supported protocols in the various places we configure protocols in Halibut.

The change has been tested in branch builds of Tentacle and Server and we have confirmed that:

• TLS 1.3 is used for tentacle communication when supported by the OS.

• TLS 1.2 is still used successfully when the platform does not support TLS 1.3.

How to review this PR

Is the current testing sufficient?

• All automated tests pass.
• We have manually tested using this configuration of Halibut in Tentacle and Server in cloud and local dev environments.

Quality ✔️

Pre-requisites

• I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
• I have considered informing or consulting the right people, according to the ownership map.
• I have considered appropriate testing for my change.

[LukeButters]

Nit: It might make sense to pull this list out to a single place and perhaps make it user configurable within the HalibutRuntimeBuilder

[LukeButters]

Approved although, Is it possible to write a test for this?