Ensure minimal context timeout for shard context APIs

[yycptt]

What changed?

• Ensure minimal 1s context timeout for shard context APIs that may lead to shard movement.

Why?

• Context timeout errors in some shard context APIs will result in shard ownership lost and the processing for the entire shard will be blocked until the shard is re-acquired. Those context may from user calls or background task processing, and we don't have good control over what's the remaining time for making the shard context API call. To minimize the impact of this persistence context change, a minimal context timeout (1s) will be enforced on shard context methods that may lead to re-acquire shard.
• Prepare for the next set of changes for actually using persistence context timeout passed into persistence store implementation.

How did you test it?

• Existing test

Potential risks

• Very low, the context is not actually used by persistence implementations

Is hotfix candidate?

• no