Unit Testing parity across dotnet, JS, Python and Java

[gabog]

The TestAdapter, TestFlow and DialogTestClient classes don't align and work differently in the different platforms.

We need to:

• [ ] Review and compare these the public methods, constructors and properties in the 4 supported platforms.
• [ ] Create issues to track the parity work based on the outcome of the analysis.

I would recommend we take the dotnet versions as the starting point and identify what's missing in the other platforms.

Additional notes

• This issue exemplifies a gap in JS TestFlow.
• TestAdapter and TestFlow work significantly different in JS and C#, TestFlow is a private class in JS and a public class in C#, and the approach for creating TestFlow is very different in both platforms.
• TestAdapter is not part of the Java framework.

[cleemullins]

This needs Analysis prior to execution.