Known JA3 token parsing issue

[Danny-Dasilva]

Actual behavior TLS handshake fails on http2 servers

Expected behavior TLS handshake succeeds on http2 servers

To Reproduce Steps to reproduce the behavior

1. use a known ja3 token and request a url with exclusive http2 support such as https://http2.pro/api/v1

Additional Information
After investigation this is a known issue with the way ja3 tokens are being parsed currently in the repo, for http1 servers this should not affect anything but for http2 servers the handshake will fail. Along with this this incorrect parsing produces an incorrect ja3 hash which can be detected. There will be a PR made as soon as this is figured out.

---

The issue can be found in the utls.SupportedCurvesExtension and utls.KeyShareExtension for chrome which uses the GREASE_PLACEHOLDER along with this the SupportedSignatureAlgorithms needs to be parsed from the JA3 string in order to generate the correct signature scheme relating to the string

[Danny-Dasilva]

SupportedSignatureAlgorithms needs to be dynamically set somehow. Everything else should not be detectable. See PR