Always allow unquoted keywords as column names

[KevinGe00]

What changes are proposed in this pull request, and why are they necessary?

This PR is a follow up to #503 and fixes #534. During integration testing with a Trino environment, the instantiation of the new HiveConf object threw failure to login: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name. This is due to the false assumption for the presence of Hive configuration files such as hive-site.xml in Trino environments, which new HiveConf() will try to look for. This PR fixes this false assumption by removing new HiveConf() and forces leniency for unquote keyword columns when parsing hive views. A long term solution will involve an engine-agnostic KV config map used ubiquitously across coral.

How was this patch tested?

• clean build
• testUnquotedKeywordAsColumnName passes when useSQL11ReservedKeywordsForIdentifier returns true and fails when useSQL11ReservedKeywordsForIdentifier returns false
• tested translation of view with unquoted keyword column on spark-shell with these coral changes
• set up local trino cluster with these coral changes, successfully ran translation for view with unquoted keyword column
• regression tests for spark and trino passes