[Pipe] Prevent resizing released TsFile scan parser memory

[Caideyipi]

Description

Problem

When TsFileInsertionEventScanParser reached EOF while producing the final tablet, prepareData() closed the parser immediately. The iterator then tried to release the parser-side tablet memory in its finally block, which called forceResize(0) on an already released memory block and could continuously emit forceResize: cannot resize a null or released memory block warnings.

Changes

• Defer parser close at EOF until after the final tablet memory accounting is released.
• Keep immediate cleanup in the constructor when a TsFile contains no tablet data.
• Strengthen the parser unit test to verify that tablet memory usage is zero before its block is closed.

Tests

• mvn spotless:apply -pl iotdb-core/datanode
• mvn -pl iotdb-core/datanode -Dtest=TsFileInsertionEventParserTest test (21 tests, 0 failures, 3 skipped)

---

This PR has:

• been self-reviewed.
• added comments explaining the why and intent of the non-obvious close ordering.
• modified an existing unit test to cover the regression.

---

Key changed/added classes

• TsFileInsertionEventScanParser
• TsFileInsertionEventParserTest