chore: Logs the duration of migrations execution

[michael-s-molina]

SUMMARY

Depending on the amount of data an organization has, the migration scripts can take a long time to run. This PR adds the duration of the complete migration process to help administrators to estimate downtime for upgrades/downgrades. Duration is only logged in case all migrations successfully complete.

TESTING INSTRUCTIONS

CI should be sufficient.

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

Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Project coverage is 83.69%. Comparing base (76d897e) to head (8fe12f2).
Report is 1094 commits behind head on master.

Files with missing lines	Patch %	Lines
superset/migrations/env.py	0.00%	9 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #29893       +/-   ##
===========================================
+ Coverage   60.48%   83.69%   +23.20%     
===========================================
  Files        1931      527     -1404     
  Lines       76236    38041    -38195     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    31839    -14275     
+ Misses      28017     6202    -21815     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	49.01% <0.00%> (-0.15%)	⬇️
javascript	?
mysql	76.78% <0.00%> (?)
postgres	76.85% <0.00%> (?)
presto	53.56% <0.00%> (-0.24%)	⬇️
python	83.69% <0.00%> (+20.20%)	⬆️
sqlite	76.33% <0.00%> (?)
unit	60.36% <0.00%> (+2.73%)	⬆️

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.

[giftig]

A couple of minor nitpicks

[mistercrunch]

[optional] a context decorator could be nice and simple for this:

with print_duration(label=f"Migration: {migration_id}"):
   do_stuff()

Wondering if just using event_logger.log_context(action='migration') would just work (in CI, the logging should be utils.log.StdOutEventLogger, though it doesn't seem to be the default)

[michael-s-molina]

[optional] a context decorator could be nice and simple for this:

That would be nice. We can think about this when creating the helper functions for the migrations as part of [SIP-142] Improving Database Migration Management