Flaky test: tests/sentry/integrations/opsgenie/test_integration.py::OpsgenieMigrationIntegrationTest::test_no_duplicate_keys

Failing test: tests/sentry/integrations/opsgenie/test_integration.py::OpsgenieMigrationIntegrationTest::test_no_duplicate_keys
Sentry sha: 4a8dadc9c184ad93a761561c5f57437a29cd3300
Run: https://github.com/getsentry/sentry/actions/runs/22283662003

tests/sentry/integrations/opsgenie/test_integration.py:381: in test_no_duplicate_keys
    assert org_integration.config == {
E   AssertionError: assert {'team_table'...[MIGRATED]'}]} == {'team_table'...[MIGRATED]'}]}
E     
E     Differing items:
E     {'team_table': [{'id': '222-thinkies', 'integration_key': '123-key', 'team': 'thinkies [MIGRATED]'}]} != {'team_table': [{'id': '222-thonk', 'integration_key': '123-key', 'team': 'thonk [MIGRATED]'}]}
E     
E     Full diff:
E       {
E           'team_table': [
E               {
E     -             'id': '222-thonk',
E     ?                          ^
E     +             'id': '222-thinkies',
E     ?                          ^  +++
E                   'integration_key': '123-key',
E     -             'team': 'thonk [MIGRATED]',
E     ?                        ^
E     +             'team': 'thinkies [MIGRATED]',
E     ?                        ^  +++
E               },
E           ],
E       }

Start with tests/sentry/integrations/opsgenie/test_integration.py and run OpsgenieMigrationIntegrationTest::test_no_duplicate_keys, using the linked Actions run and reported Sentry SHA as context. Investigate why the migration produces either the thonk or thinkies team entry; done means the test passes consistently with the expected configuration.