Make timeout for resolvers configurable

Version: 1.47.0-insider (user setup)
Commit: e95f9e63380a139cb1cbe54bacfc6703b96e30b9
Date: 2020-07-07T07:46:21.608Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

• VSCode Version: 1.47.0-insider (user setup)
• Local OS Version: Windows_NT x64 10.0.18363
• Remote OS Version: Centos 8.1 (Containers)
• Remote Extension/Connection Type: Docker (Docker desktop 2.3.0.3 (45519))

Steps to Reproduce:

1. Create a docker container and start it.
2. In the docker extension screen, CONTAINERS part, right click on the created and select "Attach Visual Studio Code".
   

Sometimes, the new VSCode window opens quickly (less than 5 seconds), with VSCode connected to the container (explorer sees all contained files, ...)
However, about 90% of the time, the new VSCode window is very slow to open (about one minute) and after around 5 minutes timeout error messages are displayed, VSCode isn't connected to the container (can't see the files ...).

The fail (timeout) :

Even if the container name is displayed in the lower left of the screen, the connection isn't properly done, the container's files aren't visible from VSCode, the terminal isn't working, ...

This behavior occurs even if the container is running locally.

Here are the logs in VSCode console

VSCodeTimeout.log

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Start with the Docker attach-to-container reproduction in the issue and review the attached VSCodeTimeout.log from the console. Trace where the resolver timeout is reported and determine the configuration entry point; done means the timeout can be configured and the setting is honored during the connection attempt.