Meltano

When we built `tap-athena` in the live coding session two weeks ago, I commented on how generic the code ended up being. The only thing Athena-specific was the <https://github.com/MeltanoLabs/tap-athena/blob/master/tap_athena/client.py#L15-L22|creation of the sqlalchemy conection string>, which concatenated the creds. We didn't yet to any Athena-specific optimizations but the result was still functional and a solid entry-level tap. Alternatively, we could get the same functionality by allowing the user to install their own driver and provide their own fully built connection string.

What do folks think of a basic `tap-sqlalchemy` or (anther name for the same thing) `tap-dbapi` (emphasis on <https://docs.sqlalchemy.org/en/14/glossary.html#term-DBAPI|DBAPI >as described in <https://www.python.org/dev/peps/pep-0249/|PEP-249>)?

Presumably, If the proper drive is installed into the virtual environment, then this could give basic interop for anything in <https://docs.sqlalchemy.org/en/14/dialects/#included-dialects|this list> or <https://docs.sqlalchemy.org/en/14/dialects/#external-dialects|this one> - as well as for community-created drivers like <https://pypi.org/project/pyathena/|PyAthena> which are not on either list. The tap would just accept as config input whatever connection string was needed for the specific requested driver.

Questions for further discussion:

1. Would this be valuable as an entry-level connector - and/or a starting point for other taps?
2. Any thoughts on the naming `tap-sqlalchemy` vs `tap-dbapi`? I think I like referencing DBAPI but curious to other's thoughts.