Replace HiveQlTranslation with a non-regex-based parser

[jirassimok]

The new parser does the same thing the regular expression was supposed to do; it just replaces the quotation marks and makes sure that any contained quotation marks are properly escaped. No other escape sequences are handled (which will cause unexpected behavior if there's an escape sequence in a Hive view).

Also, the error thrown when parsing fails needs to be replaced, but I'm not sure what fits, besides adding a new error to HiveErrorCode. Maybe HIVE_PARSE_ERROR?

This addresses #3266.

[electrum]

This seems wrong. We should fail if there are escape sequences if we're not going to handle them. Otherwise, we are returning a known invalid result.

[jirassimok]

That's a good idea. I originally tried to figure out what escape sequences Hive supports, but eventually decided against it and ended up leaving the behavior the same as it was before.

I could pretty easily cover the common cases if we want, or I suspect Hive uses ...hive.ql.parse.BaseSemanticAnalyzer.unescapeSQLString or something similar so I could try using that (I'd basically just search for the end of the string, pass the whole thing to that function, then escape only single quotes from that output).

[jirassimok]

The first new commit rejects all escape sequences, and the second uses the function I mentioned above to translate all of them. I can squash them or drop the last one depending on what we want to do.

[electrum]

Please squash the commits

[findepi]

CI failed -- #3161

[electrum]

Thanks!