fix(migration): Only attempt to drop types if they exist

[jfrag1]

SUMMARY

If the database is fully upgraded, then downgraded past this migration, re-upgrading will fail because the migration is trying to drop a type that does not exist.

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

[Antonio-RiveroMartnez]

LGTM

[codecov]

Codecov Report

Merging #23650 (de4fee7) into master (825006d) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master   #23650   +/-   ##
=======================================
  Coverage   67.93%   67.93%           
=======================================
  Files        1918     1918           
  Lines       73891    73891           
  Branches     8058     8058           
=======================================
  Hits        50199    50199           
  Misses      21633    21633           
  Partials     2059     2059           

Flag	Coverage Δ
hive	53.16% <ø> (ø)
mysql	79.21% <ø> (ø)
postgres	79.29% <ø> (ø)
python	83.03% <ø> (ø)
sqlite	77.78% <ø> (ø)
unit	53.02% <ø> (ø)

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

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