feat: allow configuring an engine context manager

[betodealmeida]

SUMMARY

This PR introduces a configurable context manager that wraps the create_engine call to analytical databases. The intended use case is to configure the Oracle driver with tenant-specific settings in a multi-tenant environment, but there are many other potential use cases for this:

1. Custom logging
2. Supressing noisy logs from 3rd party database drivers
3. chrooting to prevent 3rd party databases drivers from accessing the filesystem (maybe using pychroot)

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A

TESTING INSTRUCTIONS

Added a unit test.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[betodealmeida]

I rewrote this as a function since it's easier to read and removes the lambda complaint from the linter.

[mistercrunch]

Nice. Did grepping to check if there were some rogue create_engine calls not going through this method and it looked squeaky cleaned.

[dpgaspar]

Nice!

[betodealmeida]

Nice. Did grepping to check if there were some rogue create_engine calls not going through this method and it looked squeaky cleaned.

@mistercrunch yeah, when we implemented SSH tunneling we had to consolidate all the logic in a single place.