Support data sequence numbers in REST scan tasks

REST-planned `FileScanTask` currently parses `first-row-id` from the embedded `data-file` JSON, but the REST scan-task payload does not expose the manifest-entry data sequence number.

For v3 row lineage readers, `_last_updated_sequence_number` inheritance needs the data file data sequence number. Without it, REST-planned tasks can pass `first_row_id` but cannot inherit `_last_updated_sequence_number` for files that omit or store null row-lineage columns.

Follow-up from apache/iceberg-cpp#822. The PR adds a skipped test, `FileScanTasksFromJsonTest.RowLineageSequence`, that should be enabled once REST scan-task JSON can carry this value.

首先跟踪 REST 扫描任务的 JSON 解析，以及清单条目数据序列号的表示方式。使用被跳过的测试 FileScanTasksFromJsonTest.RowLineageSequence 作为验收检查。完成的标准是 REST 规划的任务携带数据序列号，并且针对行血缘继承的测试已启用并通过。

由索引模型根据 Issue 内容生成。