fix: Deque mutated during iteration

[michael-s-molina]

SUMMARY

Fix a bug introduced by #24488 that happens when running on SQL Lite. There was an event being registered inside another event and causing a deque mutated during iteration error. According to SQL Alchemy docs:

The listen() function cannot be called at the same time that the target event is being run. This has implications for thread safety, and also means an event cannot be added from inside the listener function for itself. The list of events to be run are present inside of a mutable collection that can’t be changed during iteration.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

• Check that the above error does not happen when accessing a dashboard on SQL Lite.
• Check that if a dataset is deleted, its associated columns and metrics are also deleted.

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

Merging #24550 (d5114b4) into master (66f59e5) will increase coverage by 0.07%.
The diff coverage is 100.00%.

❗ Current head d5114b4 differs from pull request most recent head c641a73. Consider uploading reports for the commit c641a73 to get more accurate results

@@            Coverage Diff             @@
##           master   #24550      +/-   ##
==========================================
+ Coverage   68.98%   69.05%   +0.07%     
==========================================
  Files        1906     1906              
  Lines       74114    74114              
  Branches     8155     8155              
==========================================
+ Hits        51124    51182      +58     
+ Misses      20871    20813      -58     
  Partials     2119     2119              

Flag	Coverage Δ
hive	53.92% <20.00%> (?)
mysql	79.40% <20.00%> (?)
postgres	79.49% <20.00%> (ø)
presto	53.82% <20.00%> (ø)
python	83.43% <100.00%> (+0.16%)	⬆️
sqlite	?
unit	54.69% <100.00%> (-0.01%)	⬇️

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

Impacted Files	Coverage Δ
superset/utils/core.py	91.59% <100.00%> (+0.11%)	⬆️

... and 11 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[michael-s-molina]

@hughhhh I set commit=False to mimic the other tests in the ssh_tunnel/commands folder which use CreateSSHTunnelCommand that has commit=False by default. If we enable the commit in this test or in the command ones, they will fail because there's no database with id = 1. If an actual commit is required for the tests, I suggest opening a follow-up PR and fixing not only this test but the ones in the commands folder.