feat: simplify timeout settings

[NguyenHoangSon96]

Issue Link

Proposed Changes

• I have removed the code that sets the timeout directly to HttpClient; now the timeout will be set to the function that makes an HTTP call every time users make a call. I think this makes the logic easier to implement and supports backward compatibility. We already set the default timeout for write APIs to 10 seconds. Additionally, setting the timeout directly to HttpClient will override the deadline in grpc (or maybe I'm wrong here...),
• Query and Write APIs both support setting a one-time "timeout" now, but in a different form, e.g., CancelToken for write APIs, TimeSpan for query APIs.
• Setting a timeout directly to the query or write functions will have the highest priority now.

Checklist

• CHANGELOG.md updated
• Rebased/mergeable
• A test has been added if appropriate
• Tests pass
• Commit messages are conventional
• Sign CLA (if not already signed)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.77%. Comparing base (f95b720) to head (e811c69).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   96.72%   96.77%   +0.04%     
==========================================
  Files          18       18              
  Lines        1436     1457      +21     
  Branches      191      196       +5     
==========================================
+ Hits         1389     1410      +21     
  Misses          5        5              
  Partials       42       42              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[karel-rehor]

Looks good. I just have a couple of questions about a removed test, and replacing default with null in method arguments.

[karel-rehor]

I'm not sure we want to remove this test if the ClientConfig.Timeout property has only been deprecated and not removed. Some users may continue to use it. It's reassuring to know, even though the property is deprecated, the code section continues to work.

[NguyenHoangSon96]

I removed this test and the part where we set the Timeout directly to HttpClient object because if we set the Timeout directly to the HttpClient, it will have conflicting behavior when we also set QueryOptions.Deadline.
If we set the Timeout directly to the HttpClient and set the QueryOptions.Deadline, grpc will get the smallest timeout between them, and I don't think this is the right behavior.
The new implementation will absolutely prioritize: QueryOptions.Deadline > QueryTimeout > Timeout (If the users set the Timeout property, it will not directly set the Timeout to the HttpClient, so the QueryOptions.Deadline still runs like intended ). These are my thoughts.

[karel-rehor]

Looks OK. Tests passing locally. 🚴 🏁