[python] Support target file row num for blob and vector writes

[YannByron]

Purpose

Allow pypaimon data-evolution append tables with blob or vector columns to honor target-file-row-num by keeping normal, blob, and vector writers rolling in sync on row count.

Changes

• Permit target-file-row-num for data-evolution append tables with blob/vector columns while keeping existing unsupported table checks.
• Add row-count rolling support for blob, vector, and dedicated-format writers.
• Remove redundant rolling/rethrow logic and cover the combined blob+vector path.

Tests

• python -m pytest pypaimon/tests/data_evolution_row_rolling_test.py -q
• python -m pytest pypaimon/tests/data_evolution_formats_test.py -q
• python -m pytest pypaimon/tests/vector_table_test.py -q
• python -m pyflakes pypaimon/tests/data_evolution_row_rolling_test.py pypaimon/write/file_store_write.py pypaimon/write/writer/blob_writer.py pypaimon/write/writer/data_vector_writer.py pypaimon/write/writer/dedicated_format_writer.py
• git diff --check origin/master..HEAD

[JingsongLi]

Please preserve BlobConsumer-owned blob files here. After row-count rolling, _close_current_writers transfers blob metadata to self.committed_files and clears the child writer metadata, so this unconditional deletion removes blob files even when a consumer has already received descriptors pointing to them. This differs from the Java implementation, where BlobFormatWriter.deleteFileUponAbort() returns false when a consumer is configured. With target-file-row-num=3, writing 7 rows and then aborting leaves 6 of the 7 emitted descriptors unreadable. Please retain the per-file delete-on-abort policy when transferring ownership and add a rolling + consumer + abort regression test.

[JingsongLi]

+1