[lake/tiering] add table dropped handling and nullable write results

[beryllw]

Purpose

Linked issue: close #2498

This PR improves Lake Tiering's handling of dropped tables and adds cancellation support for tiering operations.

Brief change log

Dropped Table Handling

• When a table is dropped during active tiering, the TieringSplitReader now gracefully completes all
  in-progress splits with empty results instead of failing
• Added handleTableDropped() to mark dropped tables and trigger force completion
• Dropped tables are properly cleaned up from LakeTableTieringManager to prevent resource leaks

Cancellation Support

• Added cancelled flag to TableBucketWriteResult to distinguish between normal and cancelled tiering rounds
• Committers skip commit processing for cancelled results and report back to the coordinator
• Lake writers are closed without completing when tiering is cancelled, discarding uncommitted data

Tests

API and Format

Documentation

[leekeiabstraction]

TY for the PR, left a comment.

[leekeiabstraction]

As canceled field is added, shouldn't the serialVersionUID be bumped as well? Similarly the serialiser needs to handle each version of TableBucketWriteResult differently.

[luoyuxia]

Haven't finish review, but left some comments

[luoyuxia]

if move to a split, and then the split is for the table dropped, will getOrMoveToTable cause exception and then fail the job. Maybe we can protect this case .

[luoyuxia]

IIUC, we don't need to check this exception, just wait it to be forced complete in next fetch.
Also, as disscuss before, poll won't throw TableNotExistException.