[WIP] Change min and max TLS version to v1.3 for internal encryption (between Ingress to Activator)

[izabelacg]

Proposed Changes

• Change minimum and maximum TLS version (from 1.2 to 1.3) when internal encryption is activated (between Ingress to Activator)

TLS 1.3 comes with numerous enhancements, such as a quicker TLS handshake and more secure cipher suites.

Release Note

* Activator uses TLS version 1.3 when internal encryption is activated for communication with Ingress

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: izabelacg
Once this PR has been reviewed and has the lgtm label, please assign dprotaso for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.03 ⚠️

Comparison is base (d07bf78) 86.21% compared to head (079c20c) 86.18%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13930      +/-   ##
==========================================
- Coverage   86.21%   86.18%   -0.03%     
==========================================
  Files         199      199              
  Lines       14767    14768       +1     
==========================================
- Hits        12731    12728       -3     
- Misses       1734     1737       +3     
- Partials      302      303       +1     

Impacted Files	Coverage Δ
cmd/activator/main.go	0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[izabelacg]

From #13887 (comment):

It seems TLS 1.3 between Ingress -> activator has an issue - probably related to envoyproxy/envoy#9300

Opened an issue to track this: #14057, and will close this PR.