Permissive TLS parsing

[Seanstoppable]

This is driven by #378, zmap/zcrypto#364 and #334

This allows a number of scans to actually succeed, rather than fail out when parsing the certificate

Example without permissive parsing:

echo FAILING_IP | ./zgrab2 http -p 443 --use-https
INFO[0000] started grab at 2023-09-21T21:25:29-05:00
{"ip":"FAILING_IP","data":{"http":{"status":"unknown-error","protocol":"http","result":{},"timestamp":"2023-09-21T21:25:29-05:00","error":"tls: failed to parse certificate from server: asn1: structure error: explicitly tagged member didn't match"}}}
INFO[0001] finished grab at 2023-09-21T21:25:29-05:00
{"statuses":{"http":{"successes":0,"failures":1}},"start":"2023-09-21T21:25:29-05:00","end":"2023-09-21T21:25:29-05:00","duration":"987.606886ms"}

With Permissive parsing:

echo FAILING_IP | ./zgrab2 http -p 443 --use-https
INFO[0000] started grab at 2023-09-21T21:25:34-05:00
{"ip":"FAILING_UP","data":{"http":{"status":"application-error","protocol":"http","result":{"response":{"status_line":"302 Found","status_code":302,"protocol":{"name":"HTTP/1.1","major":1,"minor":1},"headers":{"content_length":["0"],
... all the HTTP and TLS handshake log data

[mzpqnxow]

@dadrian can you consider this for merging if you have a moment? Literally a moment, probably - it's a very small change, but an impactful one in large collections, hence the nudge 😊

Thanks @Seanstoppable for submitting this, it fell completely off my radar

[dadrian]

We could probably default to this tbh

[mzpqnxow]

We could probably default to this tbh

That would be awesome- I wasn't sure how it might impact the output schemas that y'all have, and if it might break any test-cases you have, so I didn't want to be presumptuous

Probably the vast majority of users would be appreciative of it as a default

[Seanstoppable]

I'm happy to change this to be default behavior if that is the desire. Just opted to do behavioral backwards compatibility.

[Seanstoppable]

Updated to just be the default