Fix/ws timeout filter not removed

[DarianShawn]

Description

The jsonrpc filter was not removed elegantly when timeout, and might block querying even the whole program in some extreme cases.

When triggered, it kept printing log like that:

dogechain.filter: filterBase timeout: id=46eeaded-d726-4202-b4d1-f338ab1427a8 expiresAt="2022-08-25 17:56:25"
dogechain.filter: failed to uninstall filter: id=46eeaded-d726-4202-b4d1-f338ab1427a8
dogechain.filter: filterBase timeout: id=46eeaded-d726-4202-b4d1-f338ab1427a8 expiresAt="2022-08-25 17:56:25"
dogechain.filter: failed to uninstall filter: id=46eeaded-d726-4202-b4d1-f338ab1427a8
// repeated on and on...

The PR fixes this issue. Here is the solution.

We use only one timer and reset it for the timeout checking, and do nothing when the timer fired.
The timer puts down the responsibility of handling the business, its only purpose is to make the loop go round.

That makes sense.
If the node is idle, it should not wait too long for the hurry serving.
If the node is busy, it should focus on the current job instead of distracted from dealing with clutter.
And finally, It shouldn't bordered by the timeout filters, so we remove all those outdated filters once and for all.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

Manual tests

1. Set up a dev mode node.
2. Send several eth_newBlockFilter, eth_newLogFilter, eth_getFilterChanges requests using curl or WebSocket client, in order to trigger with different timeout timestamps.
3. Watch the logs.

We should find only one 'adding', 'deletion' for each filter, and never get any repeated timeout logs no matter how many times we test.

[abrahamcruise321]

lgtm.