fix: keep the coordinates in a cloned ReadCellData

[CodeMan-cmd]

Purpose of the pull request

Closed: #1131

What's changed?

A cell read as ReadCellData (a model field typed ReadCellData/CellData, or readDefaultReturn(READ_CELL_DATA)) is produced by ConverterUtils.convertToJavaObject, which clones the parsed cell. ReadCellData.clone() copied the type, the value, the data format and the formula but not rowIndex/columnIndex, so every ReadCellData handed to a listener had null coordinates even though the parsers set them and convertToJavaObject already receives both indexes as arguments. The clone now keeps them, which also matches WriteCellData, where the coordinates are set on the way out.

Measured before the change, same test, on all three formats: date(row=null,col=null) integer1(row=null,col=null) formula(row=null,col=null); after the change: date(row=1,col=0) integer1(row=1,col=1) formula(row=1,col=3).

Tests:

• CellDataDataTest asserts the coordinates of the ReadCellData fields of a round trip, for xlsx, xls and csv.
• ReadCellDataTest.cloneKeepsCoordinates is a unit test for the clone itself.

Without the fix 4 of the 5 new assertions fail, with the fix all of them pass.

Local verification with Temurin 1.8.0_472:

• ./mvnw clean package -B -Dmaven.test.skip=false -pl fesod-common,fesod-shaded,fesod-sheet -> 917 tests, 0 failures
• ./mvnw spotless:check -> Build success

Checklist

• I have read the Contributor Guide.
• I have written the necessary doc or comment.
• I have added the necessary unit tests and all cases have passed.

[skytin1004]

Thanks for the fix. I reproduced the missing coordinates with the pre-fix implementation and verified that this change preserves the row and column indexes for XLSX, XLS, and CSV. All tests passed locally with Java 11. LGTM.