feat(emulate): parse tls/http2

[0x676e67]

It now supports parsing Chrome profiles. You can obtain configurations either by manual editing or deploying the request endpoint from https://github.com/pagpeter/TrackMe. We currently only adopt its format since it supports PSK, while https://tls.browserleaks.com/ does not.

Calculation algorithms like JA3 and JA4 are not critical here; they are merely statistical hashes and cannot truly reflect real Chrome fingerprints. For newer versions, set permute_extensions: true to enable random extension shuffling.

[dhurba87]

Great improvements. Now we don’t have to wait for the gem to ship a new browser version. I believe the README needs an update.

[0x676e67]

Reasons not to use TrackMe: 0x676e67/wreq-python#598

Both https://get.ja3.zone/ and https://tls.peet.ws/api/all are deployed based on TrackMe and cannot display large request headers; oversized data will be truncated. Partial truncation also occurs on https://tls.browserleaks.com/.
It is clear that these echo test websites do not implement HTTP servers in compliance with standard RFC specifications. Only httpbin.io can fully display complete request headers without truncation.