bridgestrap should learn about TLS_ERROR ORCONN failure reason

In the bridgestrap logs I see lines like

2024/07/12 02:51:39 2e927c2f: Bug: could not find reason for "TLS"

I think it is seeing "TLS_ERROR" ORCONN reasons, which were added after bridgestrap learned about reasons, and which didn't make it into the control-spec.txt (that bug is now tpo/core/torspec#266).

It's not a big deal, because bridgestrap then says

2024/07/12 02:51:39 Setting obfs4 209[[...]sXQ iat-mode=0 to 'dysfunctional': UNANTICIPATED_ERROR

which is the same action it would have taken anyway.

The list of expected reasons is in events.go and it looks easy to add a new one.

The only remaining mystery for me is why bridgestrap says it receives "TLS" when I think Tor is saying "TLS_ERROR", but I think it's because bridgestrap is doing some sort of subset hack with

var OrConnReasonField = regexp.MustCompile(`^650 ORCONN.*REASON=([A-Z]*)`)