[SL-20310] viewer - crypto - Update libcurl and openssl versions to acquire support for SSLKEYLOGFILE envvar for https: tracing

From jira-archive-internal created by sl-service-account: secondlife/jira-archive-internal#70664

With TLS 1.3 and ephemeral DH ciphers, the old hack of supplying the server private x.509 key to Wireshark no longer enables https: decryption.  The 'modern' approach is to get a key log file generated out of the crypto package.  The current version of the viewer's libraries does not support this but it is available in commonly-installed 'curl' packages right now.  So, time to update and give the security aspects of this feature some thought.

Background:  https://daniel.haxx.se/blog/2018/01/15/inspect-curls-tls-traffic/

[ Note:  This is almost certainly dependent on getting http/2 support working to free up the libcurl version we use. ]

Links

In epic

• https://github.com/secondlife/jira-archive-internal/issues/62380

{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Epic Link': 'SL-12606',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
}

Start by tracing how the viewer currently builds and packages libcurl and OpenSSL, then verify the HTTP/2 prerequisite mentioned in the issue. Determine the required library versions and review the security implications of enabling SSLKEYLOGFILE for HTTPS tracing. Done means the supported versions provide this capability and the security treatment is documented.