fix: ignore TracingSetup error in migration tests

[m1sterc001guy]

Running cargo test causes an error with the db migration tests since the tracing subscriber is already setup. Simple fix is just to ignore the error.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (04d32a7) 58.06% compared to head (471e699) 58.02%.
Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4146      +/-   ##
==========================================
- Coverage   58.06%   58.02%   -0.04%     
==========================================
  Files         192      192              
  Lines       42972    42982      +10     
==========================================
- Hits        24951    24942       -9     
- Misses      18021    18040      +19     

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

[elsirion]

Sounds reasonable, did this lead to flakiness?

[dpc]

Sounds reasonable, did this lead to flakiness?

@elsirion Makes cargo test fail. CI is fine because cargo nextest we're using spawns every test in a different process (that's the secret sauce of it).