ref(code review): add date_updated and date_added columns to RepositorySettings

[srest2021]

fixes CW-683

Add date_updated and date_added columns to RepositorySettings for easier debugging.

Also, remove test_1016_remove_on_command_phrase_trigger.py as it was failing due to using a direct import of RepositorySettings, and we don't need this test anymore.

[linear]

CW-683 Add date_added and date_updated to sentry_repositorysettings

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/1021_add_date_added_date_updated_to_repositorysettings.py

for 1021_add_date_added_date_updated_to_repositorysettings in sentry

--
-- Add field date_added to repositorysettings
--
ALTER TABLE "sentry_repositorysettings" ADD COLUMN "date_added" timestamp with time zone DEFAULT (STATEMENT_TIMESTAMP()) NOT NULL;
--
-- Add field date_updated to repositorysettings
--
ALTER TABLE "sentry_repositorysettings" ADD COLUMN "date_updated" timestamp with time zone DEFAULT (STATEMENT_TIMESTAMP()) NOT NULL;

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

date_updated not updated during bulk upsert operations

Medium Severity

The new date_updated field uses auto_now=True, but auto_now only triggers on .save() calls. The existing OrganizationRepositorySettingsEndpoint uses bulk_create with update_conflicts=True and doesn't include date_updated in update_fields. For existing rows updated via this bulk endpoint, date_updated will remain unchanged, defeating the purpose of tracking update times "for easier debugging." The db_default=Now() only applies to INSERT operations, not UPDATE operations in the upsert.