ResultsCommandExtension: Do not dispose the VssConnection

[thomasdgx]

Fix #3219

Do not dispose the VssConnection as this seems to impact the underlying socket, which leads to sporadic exception.

If I search through the code base, then it seems that in most cases the connection is not disposed.

[thomasdgx]

@anatolybolshakov Is there a way to rerun the checks? For me it looks like that your team did an agent deployment and the latest version was broken. The unit test error seems not to be related to my changes.
Could you also forward to some expert for review? I think this bug needs to be solved urgently.

[anatolybolshakov]

Hi @thomasdgx let us take a look at this PR.
Added label to PR - to pass checks

[thomasdgx]

@anatolybolshakov All checks passed now. Is there anything I need to do? Will your team accept the changes and merge them? Can you please share some timeline estimation, as I am not sure about your internal procedures. I could imagine that you integrate external changes only once per sprint.

[thomasdgx]

@anatolybolshakov Hi Anatoly,
how can I help to get the story done? Anything left I need to do?
Ciao
Thomas

[mjroghelia]

@thomasdgx Thanks for digging into this.

@anatolybolshakov I'm going to merge this. The earlier PR @thomasdgx referenced (#2811) was based on static analysis and there were a few of the using statements that had to be reverted after it was merged.