Add test-tools feed to NuGet.config

[akoeplinger]

See #47049 (comment)

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[akoeplinger]

@Youssef1313 this means users of the nightly sdk will also need this feed when using mstest, is that a concern?

[Youssef1313]

I think either that, or maybe we can publish CodeCoverage to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json, as that's where the repo was already getting MSTest 3.9 previews. cc @fhnaseer for the Code Coverage question.

[joeloff]

My vote would be for dotnet-tools. For now, we can use test-tools to unblock the codeflow PRs because SDK has a significant number of open PRs we need to get through.

[nohwnd]

Code coverage should now push to dotnet-tools as well, re-running the original PR.

[nohwnd]

or you know what, merge this, so the other PR is unblocked, and then we can solve the usage of dotnet-tools in other PR, I don't want to step on your toes by reverting a commit when I am not 100% sure it will work :)

[akoeplinger]

I think if the package is now on dotnet-tools that makes this PR obsolete since we can actually just retrigger the tests on the blocked PRs (since they would now be able to restore the package)

[Youssef1313]

I don't yet see it in dotnet-tools: