Support data sequence numbers in REST scan tasks

[wgtmac]

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 #822. The PR adds a skipped test, FileScanTasksFromJsonTest.RowLineageSequence, that should be enabled once REST scan-task JSON can carry this value.

[u70b3]

This was generated by AI during triage.

I would like to work on this issue. Following the dependency identified here and in #822, I plan to first propose the optional task-level data-sequence-number field in the REST OpenAPI, then update the C++ REST scan-task JSON serde and enable the skipped row-lineage sequence test.