chore: remove block_filter_enable option

[quake]

What problem does this PR solve?

Two configuration options (block_filter_enable and support_protocols) are conflicting, one is off by default and one is on by default

What is changed and how it works?

Remove the block_filter_enable option.

Check List

Tests

• Unit test
• Integration test

Release note

Title Only: Include only the PR title in the release note.

[driftluo]

I think this file needs to expose the support_protocols writeup(like rpc modules), now the user doesn't know how to change it.

Another question, do we need to turn off the filter protocol by default and let the user choose whether to turn it on or not?

[quake]

I think this file needs to expose the support_protocols writeup(like rpc modules), now the user doesn't know how to change it.

added in the new commit, please review again, thanks.

Another question, do we need to turn off the filter protocol by default and let the user choose whether to turn it on or not?

I prefer turn on by default, this will result in more full nodes available to download the block filter for light client.

[zhangsoledad]

bors r+

[bors]

Build succeeded:

• ci_benchmarks_ubuntu
• ci_cargo_deny_ubuntu
• ci_integration_tests_ubuntu
• ci_linters_ubuntu
• ci_quick_checks_ubuntu
• ci_unit_tests_ubuntu
• ci_wasm_build_ubuntu