Avoid applying E2E timeout for Spark queries

[FabianMeiswinkel]

Description

4.32.1 introduced a regression when adding an end-to-end timeout enforcement for queries. The end-to-end timeout on queries is scoped to the entire Flux - so fully draining the query. That could very well take longer than 65 seconds. Reverting that part of the change - still enforcing a 65 second timeout for retrieving individual pages.

All SDK Contribution checklist:

• [x] The pull request does not introduce [breaking changes]
• [x] CHANGELOG is updated for new features, bug fixes or other significant changes.
• [x] I have read the contribution guidelines.

General Guidelines and Best Practices

• [x] Title of the pull request is clear and informative.
• [x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• [x] Pull request includes test coverage for the included changes.

[FabianMeiswinkel]

/azp run java - cosmos - spark

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).