fix(db): Convert owners triggers from BEFORE to AFTER

[seer-by-sentry]

Fixes WORKER-TCA. The issue was that: Before update trigger recursively modified the same row because the exclusion condition was not active on the worker's database connection.

• Converted PostgreSQL triggers on the owners table from BEFORE to AFTER timing (e.g., owners_before_insert is now owners_after_insert).
• This change resolves potential database errors (TriggeredDataChangeViolation) caused by BEFORE triggers attempting to modify the table they are triggered on.
• Applied the fix via migration 0011_convert_owners_trigger_to_after.py and updated the source SQL definition.

This fix was generated by Seer in Sentry, triggered by Tom Hu. 👁️ Run ID: 6606469

Not quite right? Click here to continue debugging with Seer.

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.

[codspeed-hq]

CodSpeed Performance Report

Merging #607 will not alter performance

_{Comparing seer/fix/convert-owners-trigger-to-after (3980379) with main (6f76140)}

Summary

✅ 9 untouched