test: cover RDF bloom remote dynamic filter e2e

[discord9]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

Fork-only stack PR. Stacked on PR3: #3

Earlier stack:

• PR1a upstream payload model: feat: add RDF bloom payload model GreptimeTeam/greptimedb#8354
• PR1b fork probe expression: feat: add RDF bloom probe expression #5
• PR1c fork hash lookup encoder: feat: encode hash lookup RDF bloom payloads #6
• PR2 fork wiring: feat: wire RDF bloom typed payloads #2

Depends on:

• DataFusion API PR: feat: expose dynamic filter bloom helper APIs GreptimeTeam/datafusion#9
• greptime-proto payload PR: feat(proto): add remote dyn filter bloom payload GreptimeTeam/greptime-proto#325

Part of original umbrella draft PR: GreptimeTeam#8342

What's changed and what's your intention?

This is PR 4 of the RDF Bloom stack. It adds integration coverage and implementation notes:

• adds an E2E test that builds sparse probe data and 302 build keys
• verifies SeqScan dyn_filters do not contain bloom_probe
• verifies non-pushdown Bloom FilterExec reduces rows versus its child scan
• records concise Simplified Chinese gotchas in impl-note.md

Validation run locally:

• cargo fmt --all -- --check
• git diff --check
• CARGO_PROFILE_DEV_DEBUG=0 CARGO_PROFILE_TEST_DEBUG=0 cargo check -p tests-integration
• CARGO_PROFILE_DEV_DEBUG=0 CARGO_PROFILE_TEST_DEBUG=0 cargo test -p tests-integration test_remote_dyn_filter_bloom_typed_payload_e2e --lib -- --nocapture

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.