SSL TSL 1.2 - handshake failure - SSL routines wrong signature type

### Expected Behavior

GET https REST call should be shown. With windows 10 curl (7.83.1), Postman, VS Code ThunderClient there is no issue to connect and get data.



### Actual Behavior


Preparing request to https://orbis.bvdinfo.com/api/orbis/swagger
Current time is 2023-02-03T11:10:02.016Z
Enable automatic URL encoding
Using default HTTP version
Disable SSL validation
Enable cookie sending with jar of 71 cookies
Hostname in DNS cache was stale, zapped
Trying 195.234.162.140:443...
Connected to orbis.bvdinfo.com (195.234.162.140) port 443 (https://github.com/Kong/insomnia/issues/1)
ALPN, offering h2
ALPN, offering http/1.1
TLSv1.0 (OUT), TLS header, Certificate Status (22):
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.2 (IN), TLS header, Certificate Status (22):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS header, Certificate Status (22):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (IN), TLS header, Certificate Status (22):
TLSv1.2 (IN), TLS handshake, Server key exchange (12):
TLSv1.2 (OUT), TLS header, Unknown (21):
TLSv1.2 (OUT), TLS alert, handshake failure (552):
error:0A000172:SSL routines::wrong signature type
Closing connection 1

### Reproduction Steps

_No response_

### Is there an existing issue for this?

- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Additional Information

Hello there,
I get "Error: SSL connect error". insomnia cert validation & validate certs are both disabled. Is this is a TLS1.2 issue?

Tested with insomnia 2022.7.5(build 19.01.2023) and 2023.1.0.beta.1

### Insomnia Version

2022.7.5

### What operating system are you using?

Windows

### Operating System Version

Windows 10 64 - 21H2

### Installation method

insomnia.rest

### Last Known Working Insomnia version

_No response_

No repository file, test, or entry point is named. Start by reproducing the HTTPS request on Windows with the reported Insomnia versions and compare its TLS handshake with curl or Postman; done means the request to the reported endpoint completes without the wrong-signature-type handshake failure.

Written by the indexing model from the issue text.