feat: add replay overflow limiter to rust capture

[frankh]

Problem

replay overflow works the same way the billing limiter works - we check a redis key to see if a session_id is in the overflow key, and if it is we redirect it to another topic

to be honest i don't like that we have any of this logic in the sink, i think we should be calling the sink with topic+partition_key as arguments instead of figuring them out in the sink, but perhaps that's better for a later refactor

Changes

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

added test

[benjackwhite]

As far as I understand seems to be how it should work but definitely not the authority here

[oliverb123]

I think this chunk of the code is a bit messy (generally, not due to this PR) - taking an action to refactor our kafka producer logic and possibly break it out into common, because we're gonna want to use it in other places soon too. For now, lgtm, send it (cautiously etc etc).