feat(eap): add deletion_settings to eap_items storage definition

[onewland]

Provide mechanism for lightweight deletes API to handle eap_items.

https://linear.app/getsentry/issue/EAP-283/enable-eap-items-storage-to-delete-by-trace-id

Depends on getsentry/sentry-kafka-schemas#438

Tested a delete locally by:

• setting is_enabled on the storage deletion_settings to 1
• running curl -H "Content-Type: application/json" -X DELETE http://localhost:1218/eap_items -d "@test-delete.json"

test-delete.json contents:

{
    "query": {
        "columns": {
            "project_id": [1],
            "trace_id": ["85cc9542-ef90-4282-917e-5659721fb940"]
        }
    }
}

Before and after delete:

66bbc2e1b854 :) select trace_id, count() from eap_items_1_local where trace_id='85cc9542-ef90-4282-917e-5659721fb940' group by trace_id

SELECT
    trace_id,
    count()
FROM eap_items_1_local
WHERE trace_id = '85cc9542-ef90-4282-917e-5659721fb940'
GROUP BY trace_id

Query id: f68fc09c-57df-4a53-99b8-e5653800c78a

   ┌─trace_id─────────────────────────────┬─count()─┐
1. │ 85cc9542-ef90-4282-917e-5659721fb940 │       1 │
   └──────────────────────────────────────┴─────────┘

1 row in set. Elapsed: 0.007 sec.

66bbc2e1b854 :) select trace_id, count() from eap_items_1_local where trace_id='85cc9542-ef90-4282-917e-5659721fb940' group by trace_id

SELECT
    trace_id,
    count()
FROM eap_items_1_local
WHERE trace_id = '85cc9542-ef90-4282-917e-5659721fb940'
GROUP BY trace_id

Query id: dec2a45e-1e72-4a3e-a7da-63552141fe37

Ok.

0 rows in set. Elapsed: 0.008 sec.

[MeredithAnya]

This will allow the product to make delete queries to the existing endpoint, before I had a runtime config that also enabled things to feature gate it - but anyway maybe you could use the delete_allocation_policies and set concurrent queries to 0 or something in non S4S regions?

[MeredithAnya]

@onewland okie so technically what I said is still true but since we haven't set up the topic and the topic mapping it will fail, but I mean eventually when you start testing it out

snuba/snuba/web/bulk_delete_query.py

Lines 50 to 52 in 6c487c6

	STORAGE_TOPIC: Mapping[str, Topic] = {
	StorageKey.SEARCH_ISSUES.value: Topic.LW_DELETIONS_GENERIC_EVENTS
	}

[onewland]

Given the total volume of deletes we expect, I think we should trend toward there being only one lightweight delete topic. Messages already contain the storages they delete for and consumer groups could ignore delete messages for other storages (the subscription scheduler does this for followed consumer groups).

Having said that, I'm willing to keep this as-is for now because we're probably going to delete search issues at some point and then eap-items really will be the only storage for the delete pipeline.

I'll also change this to be is_enabled=0 or find some way to disable it before deploying

[codecov]

✅ All tests passed in 1255.79s