Disable TLS 1.0/1.1 support in `curl_certificate` table

I see the runtime configuration is sufficient to prevent TLS 1.0/1.1 negotiation. In osquery/remote/transports/tls.cpp:172-173:

https://github.com/osquery/osquery/blob/3ea7d4a5283d28442f55beb4340222d8437d8b91/osquery/remote/transports/tls.cpp#L172-L173

This prevents osquery from ever negotiating those protocols on its TLS connections.

The curl table also inherits all these TLS transport options, via osquery::http::Client.

https://github.com/osquery/osquery/blob/3ea7d4a5283d28442f55beb4340222d8437d8b91/osquery/tables/networking/curl.cpp#L45

But it looks like curl_certificate table does not set the options to disable TLS 1.0/1.1.

https://github.com/osquery/osquery/blob/3ea7d4a5283d28442f55beb4340222d8437d8b91/osquery/tables/networking/curl_certificate.cpp#L289

There is no subsequent call to SSL_CTX_set_options() to disable TLS 1.0/1.1, and no cipher suite is configured. The context uses whatever OpenSSL's compiled-in defaults provide. Since the build does not pass no-tls1 or no-tls1_1 to OpenSSL's configure, TLS 1.0 and 1.1 remain negotiable from curl_certificate.

So disabling TLS 1.0 and 1.1 in the build, like PR #8213 would do, would also be good defense-in-depth by passing no-tls1 and no-tls1_1 to the OpenSSL configure step.

Compare the TLS setup in osquery/remote/transports/tls.cpp:172-173 and osquery/tables/networking/curl.cpp:45 with the SSL context created at osquery/tables/networking/curl_certificate.cpp:289. Verify how curl_certificate configures protocol options and the OpenSSL build settings related to PR #8213; done means TLS 1.0 and 1.1 cannot be negotiated through this table.