Contribution proposal: support multiconfiguration pipelines

Azure DevOps provided multiconfiguration pipelines. These pipelines will execute multiple configuration (such as debug & release) for a build. These distinct configurations potentially produce multiple log files that should be aggregated together in the viewer. Generally, however, it does not make sense to merge the logs from two build configurations.

For example, a pipeline might support a debug and a retail build. Each build might produce a log file for Binskim and for Roslyn. The viewer should either show the merged results for the debug Binskim/Roslyn files or the merged release Binskim/Roslyn log files.

SARIF provides a logical id that can be used to understand the broader set of log files to which a specific tool log belongs. This could be one mechanism to solve the problem (but will require results producers to properly emit SARIF that organizes results).

Alternately, configurations could be inferred from output location, file name convention, or some other mechanism.

No files, tests, or entry points are named. Start by reviewing how the viewer groups and aggregates SARIF log files, then investigate whether SARIF logical IDs or output naming can identify configurations. Done means the viewer can select or display results for one build configuration without incorrectly merging distinct configurations.