ref(profiles): Remove the ingest-profiles Arroyo consumer

[untitaker]

The ingest-profiles Arroyo consumer has been replaced by taskbroker passthrough mode (STREAM-1041), which consumes the profiles topic directly and dispatches process_profile_from_kafka tasks. This removes the now-dead consumer and the leftover glue around it.

Changes

• Drop the ingest-profiles entry from KAFKA_CONSUMERS.
• Delete the sentry.profiles.consumers package entirely (ProcessProfileStrategyFactory, the Arroyo process_message wrapper, and the killswitch/sampling helpers).
• Move the killswitch and sampling helpers (_should_drop / _is_sampled) into task.py, inlined into process_profile_from_kafka (always inline — no .delay() indirection, dict-only headers).
• Demote process_profile_task from an @instrumented_task to a plain function. It is no longer dispatched as its own task (only called inline from the passthrough task).
• Remove the now-empty ingest.profiling namespace. No tasks remain in it — the live passthrough task uses ingest.profiling.passthrough — and nothing else references it.
• Update tests: move the relocated cases into tests/sentry/profiles/test_task.py, drop the profiles backpressure tests (that step no longer exists), and remove ingest-profiles from the no-DLQ exemption list.

The profiling.killswitch.ingest-profiles option is retained since it is still enforced in process_profile_from_kafka. The devservices taskbroker passthrough entries (the replacement) are unchanged.

ref STREAM-1194

[linear-code]

STREAM-1194

[getsentry-bot]

PR reverted: 0508e3e

[github-actions]

Backend Test Failures

Failures on e583f4f in this run:

tests/snuba/api/endpoints/test_organization_group_index_stats.py::GroupListTest::test_platform_tag_collision_badge_resolved_correctly — log

[gw1] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/snuba/api/endpoints/test_organization_group_index_stats.py:294: in test_platform_tag_collision_badge_resolved_correctly
    assert response.data[0]["filtered"]["count"] == "3"
E   AssertionError: assert '0' == '3'
E     
E     �[0m�[91m- 3�[39;49;00m�[90m�[39;49;00m
E     �[92m+ 0�[39;49;00m�[90m�[39;49;00m

tests/sentry/issues/endpoints/test_group_events.py::GroupEventsTest::test_platform_tag_collision_resolved_correctly — log

[gw0] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/issues/endpoints/test_group_events.py:642: in test_platform_tag_collision_resolved_correctly
    assert len(response.data) == 3
E   assert 0 == 3
E    +  where 0 = len([])
E    +    where [] = <Response status_code=200, "application/json">.data

tests/sentry/issues/endpoints/test_group_event_details.py::GroupEventDetailsHelpfulEndpointTest::test_platform_tag_collision_resolved_correctly — log

[gw0] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/issues/endpoints/test_group_event_details.py:580: in test_platform_tag_collision_resolved_correctly
    assert response.status_code == 200, response.content
E   AssertionError: b'{"detail":"No matching event found. Try changing the environments, date range, or query."}'
E   assert 404 == 200
E    +  where 404 = <Response status_code=404, "application/json">.status_code