Configurable parameters for ProcDump

[mihaipetroniuandrei]

Description

Currently, ProcDumpArgsBuilder.cs contains some hardcoded parameters for ProcDump:

vstest/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/ProcDumpArgsBuilder.cs

Line 20 in 131ca14

StringBuilder procDumpArgument = new StringBuilder("-accepteula -e 1 -g -t ");

and here:

vstest/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/ProcessDumpUtility.cs

Line 21 in 131ca14

"ACCESS_VIOLATION"

We'd like to have these parameters wholly configurable through .runsettings to fit our needs.
For example, we'd like to be able to disable First Chance exceptions, to avoid unnecessary dumps for handled ACCESS_VIOLATION exceptions (weird, but it happens when working with unreliable libraries).

Steps to reproduce

Create a test that randomly throws ACCESS_VIOLATION but has _try/_except guards to catch it.

Expected behavior

BlameDataCollector has options to disable ProcDump First Chance and avoid creating a dump.

Actual behavior

The run creates a dump.

[ShreyasRmsft]

@mihaipetroniuandrei we would welcome contributions and would provide any assistance needed to contribute.