Component

rpc

Describe the feature you would like

when using PollerStream with rpc providers, filters often get dropped at some point. this should cause the poller to be stopped but the current logic for this is not very robust.
tenderly for example just returns an error code and no message, this makes it hard to implement logic for resetting the filter.

it would be nice to allow consumers of PollerStream to optionally provide the response codes that should cause the poller to stop, if received.

Additional context

No response