[FEATURE] DDC timeout to be configurable via application's env

### Feature Description

DDC flows where connector takes the responsibility of collecting device data usually has a script injected on client's end. Due to an external script going collecting the device data, there is usually a timeout associated with it for avoiding the user to be on the redirection page indefinitely. Today, these timeouts are hardcoded. Aim is to make these timeout limits configurable via application's ENV

Relevant file - https://github.com/juspay/hyperswitch/blob/main/crates/router/src/services/api.rs#L2100

### Possible Implementation

TBA

### Have you spent some time checking if this feature request has been raised before?

- [x] I checked and didn't find a similar issue

### Have you read the Contributing Guidelines?

- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

None

Start at crates/router/src/services/api.rs around line 2100 and trace how DDC timeout limits are currently applied. Identify the application's ENV configuration path and determine the expected behavior for configured and unset values; done means the timeout can be controlled through ENV without leaving the current behavior ambiguous.

Written by the indexing model from the issue text.