Improve empty wallet filtering to handle malicious RPC providers

[bdrhn9]

Currently, when filtering empty wallets, Airseeker attempts to retrieve balances using all providers simultaneously using Promise.any approach. This means that the response from the first successful RPC call is accepted, and the filtering is performed based on that response. However, in certain situations where there are malicious or out-of-sync RPC providers, they may incorrectly report non-empty wallets as empty. This can cause Airseeker to become blocked.

To address this issue, instead of using Promise.any, the responses from RPC providers can be logically combined using an OR operation. By doing this, Airseeker can avoid the problem of relying on a single potentially unreliable provider. It's important to note that the opposite scenario (reporting empty wallets as non-empty) is also possible, but it will result in behavior similar to Airseeker without the filteringEmptyWallet feature, which is not problematic.

[bbenligiray]

Note that we don't necessarily need to wait for all promises to resolve to implement this. As soon as a provider reports that the sponsor wallet is funded, we should filter the wallet in and don't wait for the other providers. We filter a sponsor wallet out only if all providers time out or report that the wallet is not funded.