Strictly isolate pipe visibility and fix zstd compression IT

[Caideyipi]

Description

• Make pipe management visibility follow the SQL dialect stored in source parameters instead of capture.tree/capture.table.
• Keep capture semantics unchanged for cross-capture and double-living pipes.
• Update isolation IT expectations and add unit coverage for dialect-based pipe visibility.
• Fix IoTDBPipeSinkCompressionIT#testZstdCompressorLevel by asserting synced data after the valid zstd-level pipes start, avoiding a flaky count timeseries assertion on historical TsFile/schema visibility.

Tests

• mvn -Ddevelocity.off=true -pl iotdb-core/node-commons -Dtest=VisibilityUtilsTest test
• mvn -Ddevelocity.off=true -pl integration-test -P with-integration-tests spotless:check
• mvn -pl integration-test -P with-integration-tests spotless:apply
• git diff --check

Targeted IoTDBPipeSinkCompressionIT#testZstdCompressorLevel execution was attempted, but local verification was blocked before IT execution by unrelated datanode generated aggregation compile errors with -am; without -am, Maven could not resolve several remote 2.0.7-SNAPSHOT artifacts.