[Feature request] Add timeout to the authentication stage for the replication

[heww]

In some customer environments, the network is not very fluent for the replication jobs. The time required to pull the blobs is unknown, but we can assume that the authentication stage should be successful quickly.

Here are net packets in our customer env when the replication job requests the token for the ACR through a proxy server.
The request hangs for 37 minutes and then the proxy server sends a RST to the harbor. Finally, harbor meets a such error read tcp 10.117.6.6:xxxx->10.221.0.48:80: read: connection reset by peer

It's better to add a timeout (eg, 5m) for the authentication stage of the replication.