[fix](arrow-flight-sql) Fix arrow flight sql query profile and correct close

[xinyiZzz]

What problem does this PR solve?

1. Fix the bug that caused finalizeQuery to fail, the query status in the profile was always RUNNING, not OK.
2. Arrow Flight is a stateless protocol, FE cannot know when the Client has completed fetching data. therefore, when the query profile returns isDone=true, it is considered that the query has ended and executes finalizeArrowFlightSqlRequest.
3. After the above fix we can get an accurate query profile, so I did some performance testing again and got the following conclusion (I had the same conclusion on Arrow 15.0.2)

// Note: The time cost may be much longer than the actual query execution time.
// You may get `cost: 700ms` here, but the query time in Doris FE's query profile is only `20ms`.
// It may be that the process of Java generating QueryResult is too slow,
// Does Arrow Flight do row-column conversion when generating QueryResult?
// Because the time taken to generate ResultSet is similar to that of Jdbc DriverManager,
// is Arrow cheating us? :) which is worth further research.
// In addition, the speed of AdbcStatement/QueryResult generated by JdbcDriver seems to be
// faster than FlightSqlDriver, this seems like a joke.

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[xinyiZzz]

run buildall

[xinyiZzz]

run buildall

[github-actions]

We're closing this PR because it hasn't been updated in a while.
This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you'd like to revive this PR, please reopen it and feel free a maintainer to remove the Stale tag!