MINIFICPP-2133 Add TLS 1.3 support

[lordgamez]

• Upgrade Asio to version 1.28.1
• Enable TLS 1.3 in version setting of HTTPClient
• Remove restricting TLS version to 1.2 in asio socket connections
• Enable TLS 1.3 in ListenTcpTests
• Move retrieving local and remote addresses after accepting connection to avoid reading remote address after the connection has already been closed by remote client
• Shutdown SSL properly to avoid stream truncated errors: https://stackoverflow.com/questions/25587403/boost-asio-ssl-async-shutdown-always-finishes-with-an-error
• Fix tests to not expect error failed handshake in case of missing certificate as of TLS 1.3 handshake failure is only detected by the client on the first read operation: https://stackoverflow.com/questions/62459802/tls-1-3-client-does-not-report-failed-handshake-when-client-certificate-verifica

By the time the client sends its "Finished" message, it has already received the "Finished" and so the handshake has completed and it can immediately start sending application data.

This of course means that the client won't know whether the server has accepted the certificate or not until it next reads data from the server.

• Only enable legacy SSL versions if legacy version is requested

Depends on #1599

https://issues.apache.org/jira/browse/MINIFICPP-2133

---

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced
  in the commit message?

• Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

• Has your PR been rebased against the latest commit within the target branch (typically main)?

• Is your initial contribution a single, squashed commit?

For code changes:

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE file?
• If applicable, have you updated the NOTICE file?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

[szaszm]

Can we collect the affected parts, and which SSL/TLS versions are accepted in each case? I think we should aim to only accept TLS 1.2 and 1.3 in all cases, unless the user explicitly allows deprecated/insecure versions.

[lordgamez]

Can we collect the affected parts, and which SSL/TLS versions are accepted in each case? I think we should aim to only accept TLS 1.2 and 1.3 in all cases, unless the user explicitly allows deprecated/insecure versions.

This is the case currently. We only support TLS 1.2 and 1.3, only HTTPClient has the option to set a specific or a minimum/maxiumum version that would allow the use of a legacy TLS version.