remove SQL metrics from worker tasks

[matt-codecov]

i don't think anyone but me ever actually used these metrics? i am going to delete them, and delete the exposure logging in the Feature system in shared, to cut down on writes and logs and whatall

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[seer-by-sentry]

🚨 Sentry detected 7 potential issues in your recent changes 🚨

• 95% chance FATAL at Line 394, tasks/base.py: Incorrect commit type leads to incorrect data and index out of range.
• 95% chance FATAL at Line 394, tasks/base.py: Incorrect commit type leads to corrupted report data.
• 95% chance FATAL at Line 394, tasks/base.py: Incorrect commit argument type causes transaction errors.

Lower risk findings

• 0% chance WARNING at Line 392, tasks/label_analysis.py:
• 0% chance WARNING at Line 392, tasks/label_analysis.py:
• 0% chance WARNING at Line 70, tasks/label_analysis.py:
• 0% chance WARNING at Line 70, tasks/label_analysis.py:

[adrian-codecov]

Approved pending tests fixed, and confirmation from the team nobody needs/wants this feature

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.77%. Comparing base (a96d25e) to head (b9f4f75).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1136      +/-   ##
==========================================
- Coverage   97.79%   97.77%   -0.02%     
==========================================
  Files         446      444       -2     
  Lines       36799    36637     -162     
==========================================
- Hits        35986    35821     -165     
- Misses        813      816       +3     

Flag	Coverage Δ
integration	42.90% <100.00%> (+0.02%)	⬆️
unit	90.47% <100.00%> (-0.06%)	⬇️

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.

[matt-codecov]

and confirmation from the team nobody needs/wants this feature

if they need/want this feature we need to recreate the tables with partitions anyway. when i last tried months ago queries were so slow that metabase couldn't even run the query for a single day

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ DataError: ["raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely"] app.tasks.upload.PreProcessUpload View Issue
• ‼️ DataError: ["raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely"] app.tasks.upload.Upload View Issue
• ‼️ ConnectionError: Error 104 while writing to socket. Connection reset by peer. app.tasks.cache_rollup.CacheTestRollupsRedisTask View Issue
• ‼️ TypeError: TestResultsProcessorTask.run_impl() missing 1 required positional argument: 'previous_result' app.tasks.test_results.TestResultsProcessor View Issue
• ‼️ ChordError: Dependency f3c22af4-db01-43de-bb5d-216809c0c236 raised TypeError("TestResultsProcessorTask.run_impl() missing 1 required positional argument: 'previous_result'") app.tasks.test_results.TestResultsProcessor View Issue

_{Did you find this useful? React with a 👍 or 👎}