There are 2 changes here
1. Move some of the helpers from test_util to tools_util since the helpers are not depended on the helper binary and can work without any dependencies
2. Introduce TriggerAutomation.bat, which triggers the automation process.

The reason we need a bat file to trigger this and not a csx or a new csx is because running the csx requires the helper binary. Hence we need to run the csx files from the binaries folder but we cannot have binaries in place if we dont fetch them in the first place. This is a cyclic problem that has to be broken with the help of one initial Trigger Batch file

Few other fixes

This change makes the csx files in the performance tool to use new ninary helper rather than use the helpers in csx
Advantages:
1. Type unification - types used in different compilation across the csx runs can unified. No need to use dynamic
2. With more helper code in CS project we get the goodness of language services when working with these files
3. With various entry points to the scripts, it is tough to understand what variables are set at various stages of the run

Also when #load a csx, I have added a comment to mention why we are `#load`ing the csx. This is easy to track when the code gets refactored and removing stale code

Rebased onto future branch
Fixed Tuple field signatures
Fixed tests affected by tuple parsing

to the RoslynPerf hive.

* remove old syntax tree root tests

* fix vb tests

This change enables the test csx files to provide the scenarios that needs to be monitored within a test execution

This enables multiple scenarios cases as well

This reverts commit 31377ce7.

This reverts commit 7debfc47.

This reverts commit a03d8b8e.

This reverts commit 29587ac2.

This reverts commit 689830b1.

This reverts commit 359eba13.

Update TargetFrameworkVersions.