Remote - Containers - Test results

Info:

1. Dotnet sdk version: 2.2.402
2. Unit test framework and relevants versions of that: xunit 2.4.0

Repro:


1. Open vs code
2. Open workspace in docker (using Remote - Containers extension)
3. Install ".Net Core Test Explorer" within the Dev Container
4. Nav to the test window
5. Select test
6. Run selected test
7. Wait forever
8. Take a look at the logs:
```
Executing dotnet test --no-build --logger "trx;LogFileName=/tmp/test-explorer-U49mqd/0.trx" --filter "FullyQualifiedName={testnamehere}" in {folder here}
Process 4989 started
Process 4989 finished
```
But nothing out of this line: https://github.com/formulahendry/vscode-dotnet-test-explorer/blob/387e0b2acba5e0624cb6c3acf365bfcd89ae2001/src/testCommands.ts#L174
9. Check if ```/tmp/test-explorer-U49mqd/0.trx``` exists, it does.

Seems like chokidar's event is never triggered for a new test result when running inside a docker container.

Start at src/testCommands.ts around line 174 and reproduce the reported flow inside a Docker-based Remote - Containers workspace. Inspect how chokidar watches /tmp/test-explorer-U49mqd/0.trx after dotnet test exits, then verify that the existing .trx result is detected and the selected test finishes instead of waiting indefinitely.

Written by the indexing model from the issue text.