retry stale read on follower if leader timeout

[mittalrishabh]

issue number : tikv/tikv#17422

Currently stale read is always retried as leader read or follower read. Follower read can overwhelm the leader if is leader raft state machine is slow.
In this fix, request is retried as stale reads to replica if leader read returns deadline_exceeded error.

After this fix :
If original request is doing stale read
Retry 1 : Try Leader read
if error is deadline exceeded
Retry 2 : Try replica 1 with stale read
Retry 3 : try replica 2 with stale read

If there is any other error
Retry 2: Try replica 1 with follower read
Retry 3 : Try replica 2 with follower read

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign you06 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• 98c36b1 retry stale read on follower if leader timeout
• d3a5edf Update region_request.go

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.