chore(tests): Fix MySQL logic

[john-bodley]

SUMMARY

Whilst spelunking through the tests, I realized that there was quirky logic for handle some atypical MySQL behavior. This seems to no longer be required, most probably as a byproduct of #28628.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

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 83.75%. Comparing base (76d897e) to head (f736fb3).
Report is 358 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #29356       +/-   ##
===========================================
+ Coverage   60.48%   83.75%   +23.26%     
===========================================
  Files        1931      518     -1413     
  Lines       76236    37624    -38612     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    31511    -14603     
+ Misses      28017     6113    -21904     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	48.90% <ø> (-0.26%)	⬇️
javascript	?
mysql	77.32% <ø> (?)
postgres	77.40% <ø> (?)
presto	53.51% <ø> (-0.30%)	⬇️
python	83.75% <ø> (+20.26%)	⬆️
sqlite	76.85% <ø> (?)
unit	59.20% <ø> (+1.58%)	⬆️

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.