kafka/server/tests: re-record deficits when retrying throttle checks

Replacing a token bucket whose rate changed discards the bytes recorded
into it, so an update landing between a record and the matching read
yields a zero delay. The old spin re-read with zero bytes, so it could
never recover and only turned the race into a 5s timeout.