feat(db_engine): Add custom_user_agent when connecting to MotherDuck

[guenp]

SUMMARY

This PR adds a custom_user_agent key to the config that is passed to the SQLAlchemy engine for DuckDB. This is needed for MotherDuck so we can track usage of Superset.
The PR also updates the sqlalchemy_uri_placeholder for DuckDB and MotherDuck.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

User agent before:

duckdb/v0.9.2(osx_arm64) python duckdb_engine/0.11.2(sqlalchemy/1.4.36)

User agent after:

duckdb/v0.9.2(osx_arm64) python duckdb_engine/0.11.2(sqlalchemy/1.4.36) apache-superset/0.0.0-dev

sqlalchemy_uri_placeholder before:

sqlalchemy_uri_placeholder after:

TESTING INSTRUCTIONS

Run unit tests.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.89%. Comparing base (d69a187) to head (ec44431).
Report is 1305 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #27665      +/-   ##
==========================================
+ Coverage   67.47%   69.89%   +2.41%     
==========================================
  Files        1911     1911              
  Lines       75019    75033      +14     
  Branches     8352     8352              
==========================================
+ Hits        50620    52445    +1825     
+ Misses      22349    20538    -1811     
  Partials     2050     2050              

Flag	Coverage Δ
hive	48.92% <37.50%> (?)
mysql	77.86% <37.50%> (-0.05%)	⬇️
postgres	78.00% <37.50%> (-0.02%)	⬇️
presto	53.63% <37.50%> (?)
python	83.16% <100.00%> (+4.99%)	⬆️
sqlite	77.44% <37.50%> (-0.02%)	⬇️
unit	56.77% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[betodealmeida]

Nice!

[guenp]

I can repro the failing CI step locally, but it succeeds if I set flask back to 2.2.5 (this was changed in #27657).
These are the errors (also happening on master):

Run pylint -j 0 superset
************* Module superset.models.helpers
superset/models/helpers.py:39:0: E06[11](https://github.com/apache/superset/actions/runs/8452926923/job/23154446091?pr=27665#step:5:12): No name 'escape' in module 'flask' (no-name-in-module)
superset/models/helpers.py:39:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.models.sql_lab
superset/models/sql_lab.py:28:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.tags.models
superset/tags/models.py:22:0: E0611: No name 'escape' in module 'flask' (no-name-in-module)
************* Module superset.views.database.mixins
superset/views/database/mixins.py:19:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.views.chart.mixin
superset/views/chart/mixin.py:[17](https://github.com/apache/superset/actions/runs/8452926923/job/23154446091?pr=27665#step:5:18):0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.connectors.sqla.views
superset/connectors/sqla/views.py:21:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.connectors.sqla.models
superset/connectors/sqla/models.py:36:0: E0611: No name 'escape' in module 'flask' (no-name-in-module)
superset/connectors/sqla/models.py:36:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)
************* Module superset.utils.core
superset/utils/core.py:63:0: E0611: No name 'Markup' in module 'flask' (no-name-in-module)

It looks like other PRs are failing with the same issue

Edit: this is now resolved but Python integration is failing.
Edit: this is now ready to merge! :)

[guenp]

@betodealmeida Thanks for the review! this PR is now ready to merge ✅