[KYUUBI #6869]Fix Beeline SQL querying cannot be stopped immediately by pressing Ctrl-C.

[Whojohn]

🔍 Description

Issue References 🔗

This pull request fixes #6869

Describe Your Solution 🔧

Expose isCancelled in KyuubiStatement ;And expose beeline cancelImmediate for user.

Why are the changes needed?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How was this patch tested?

This PR should recover CI and include negative and positive cases ;

Was this patch authored or co-authored using generative AI tooling?

No

[pan3793]

cc @link3280 @wForget

[pan3793]

the Kyuubi BeeLine is derived from Hive BeeLine(which is derived from SQLLine), does upstream BeeLine/SQLLine have similar functionalities?

[Whojohn]

the Kyuubi BeeLine is derived from Hive BeeLine(which is derived from SQLLine), does upstream BeeLine/SQLLine have similar functionalities?

SQLLine combine with flink jdbc without those problem.(BeeLine not test yet.)

SQLLine without those problem because cancel is work.

The fix way i try as fllow:

1. Fix cancel problem
   When pressing Ctrl-C, Beeline calls statement.cancel. However, the AbstractOperation#cancelOperation and OperationManager#cancelOperation checks the state in the cleanup method, causing the cancel operation to be ignored if the state is FINISHED. This issue is due to kyuubi Flink's state being FINISHED, which is not allowed in the current state check. To fix this problem, it seems that the cancel operation does not finish the Flink fetch, causing Beeline to continue calling result.next. The more I try to fix it, the more I find it breaks through too many mechanisms.
2. Fix this in BufferedRows as this pr done. (Because from now beeline depends on resultset.next but ignore cancel is calling.)

By the way flink sql cancel stuck problem is more complex. Those i fix just consider data keep coming.