[server][dvc] Add configurable client-side transfer timeout

[jingy-li]

Problem Statement

In this PR: #1805, we removed the client-side timeout and relied solely on the server-side timeout. However, in the DVC use case, we observed scenarios where the client never receives any response—neither success nor failure—from certain hosts, resulting endless bootstrap.

One such case is: the client sends a request to the server, the server receives it, generates the snapshot, and begins the transfer. However, immediately afterward, the server host starts bootstrapping, which interrupts the transfer process entirely. The client, unaware of this interruption, continues waiting indefinitely for a response.

Solution

Therefore, this PR reintroduces the client-side timeout logic and makes the timeout duration configurable.

Code changes

• Added new code behind a config. If so list the config names and their default values in the PR description.
• Introduced new log lines.
  • Confirmed if logs need to be rate limited to avoid excessive logging.

Concurrency-Specific Checks

Both reviewer and PR author to verify

• Code has no race conditions or thread safety issues.
• Proper synchronization mechanisms (e.g., synchronized, RWLock) are used where needed.
• No blocking calls inside critical sections that could lead to deadlocks or performance degradation.
• Verified thread-safe collections are used (e.g., ConcurrentHashMap, CopyOnWriteArrayList).
• Validated proper exception handling in multi-threaded code to avoid silent thread termination.

How was this PR tested?

• New unit tests added.
• New integration tests added.
• Modified or extended existing tests.
• Verified backward compatibility (if applicable).

Does this PR introduce any user-facing or breaking changes?

• No. You can skip the rest of this section.
• Yes. Clearly explain the behavior change and its impact.

[gaojieliu]

Thanks for the fix.