Opensearch operator set connection type

[Lukas1v]

---

We ran into issues when trying the Opensearch operator to connect to an endpoint with a self-signed certificate. It even failed with the following connection settings:

{
  "use_ssl": "True",
  "verify_certs": "False"
}

Those parameters were converted to strings and not as booleans.

Another issue we faced is that the connection type RequestsHttpConnection did not work for us. We discovered it because we knew the Opensearch client itself worked which uses by default a Urllib3HttpConnection, but the hook does not.

This PR addresses both issues:

• The parameters use_ssl and verify_certs are both converted to boolean in the hook
• an option is provided to specify an existing Opensearch connection type. If nothing is provided, RequestsHttpConnection is used as the default

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[Taragolis]

It even failed with the following connection settings:

{
"use_ssl": "True",
"verify_certs": "False"
}

{
    "use_ssl": true, 
    "verify_certs": false
}

[cjames23]

Looks good to me.