feat: Implementing client side statements in dbapi (starting with commit)

[ankiaga]

Implementation to Commit the ongoing transaction whenever execute() method of Cursor is called with a sql query "COMMIT" (or "COMMIT TRANSACTION")
The plan is to later add more client side statements

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[aseering]

Thanks for putting this together! No major concerns but a bunch of little comments. Let me know what you think.

[ankiaga]

Thanks @aseering for taking out time and providing valuable comments. Got to learn a lot from your comments

[asottile-sentry]

this pulls in two new dependencies (deprecated, wrapt) into this library -- this can be replaced entirely with this inside the function body:

warnings.warn("This method is deprecated.  Use classify_statement method instead", stacklevel=2)

this uses warnings directly avoiding the two new dependencies (including one which has a C extension!)

[asottile-sentry]

would one be open to a PR to do this instead?

[olavloite]

@ankiaga Would you mind taking a look what would be the best solution here?

[asottile-sentry]

threw one together: #1120