Use str type for driver and name in HiveDialect

[Usiel]

PyHive's HiveDialect usage of bytes for the name and driver fields is not the norm is causing issues upstream: apache/superset#22316
Other dialects within PyHive already use strings. While SQLAlchemy does not strictly require a string, all the stock dialects return a string, so I figure it is heavily implied.

I think the risk of breaking something upstream with this change is low (but it is there ofc). I figure in most cases we just make someone's str(dialect.driver) expression redundant. To be extra safe we could just go for a major version bump.

Examples for some of the other stock sqlalchemy dialects (name and driver fields using str): https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/sqlite/pysqlite.py#L501https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/sqlite/base.py#L1891https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/base.py#L2383https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/mysqldb.py#L113https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/pymysql.py#L59

PS: I have submitted the CLA.

[CLAassistant]

All committers have signed the CLA.

[bkyryliuk]

@Usiel can you confirm that apache/superset#22316 is addressed with this PR ?

[Usiel]

@Usiel can you confirm that apache/superset#22316 is addressed with this PR ?

Yes, this fixes the issue on Superset (I also made a comment on that issue).

[kashifjavedaddo]

@Usiel so how do i get this fixed on my installation.

do I need to upgrade my existing superset 2.1.0 installation ?

Please update with exact steps to get this done.

[Usiel]

Thanks for the merge @bkyryliuk! Will there be a release for this on PyPI?
Can confirm that by installing the current master with pip install git+https://github.com/dropbox/PyHive.git I can fix the linked Superset issue.