Fix unnecessary cancel requests

[Flgado]

Overview

This PR fixes unnecessary delete requests when the query is already finished.

Explanation

This change addresses Issue #102

• When using QueryRow followed by a Scan, the Trino driver first calls the Next method and then the Close method. The Close method triggers a delete request to cancel the query, even when the query has already completed.
• My initial approach was to use nextUri in the Close method instead of directly calling /v1/query/queryId, as suggested in the documentation and implemented by other drivers. However, to make this work, I needed to always update rows.nextUri inside the fetch method, as it was previously retaining only the first URI set here. Despite these changes, the issue persisted.
• To resolve this, I modified the Next method so that when all rows have been read, it fetches the next set of rows. This works because our fetch method, along with the running Goroutines, follows nextUri until data is retrieved.
  • For QueryRow, this ensures that when the query reaches the finished state with no more data, nextUri is cleared, preventing an unnecessary request on Close().
  • For QueryContext, this is also fine because it fetches the next batch of data, ensuring that additional data (if available) is retrieved correctly.

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[nineinchnick]

@cla-bot check

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[Flgado]

@nineinchnick add a need unit test. I think it make sense