Run wasm console sample on Helix

[MaximLipnin]

• Included the WASM console sample project to the library test build. The sample can still be built/run locally using make file.
• Added zipping/copying the sample application to helix directory from where it can be consumed by CI.
• To run on Helix, tried to use a simple helix work item which wouldn't rely on generated RunTests.sh and just call the xharness command directly.

Relates to #43865

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[radical]

@MaximLipnin does the sample run on helix now? Can you share a link to the log? I wasn't able to get to it.

[MaximLipnin]

@radical yeah, it should, please take a look at logs:

https://helix.dot.net/api/jobs/d971e44a-7a7c-42b5-92cf-36565dc3a4c6/workitems/WasmConsoleSample?api-version=2019-06-17

https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-45768-merge-d971e44a7a7c42b592/WasmConsoleSample/console.56eedcdd.log?sv=2019-07-07&se=2021-01-04T18%3A46%3A00Z&sr=c&sp=rl&sig=fqaYZNVFNghjNifRWWmDVXyeRYmwFOOSqkF6SAz8lGc%3D

[radical]

@akoeplinger would be able to review this well. I don't know enough about the helix related bits.

• I'm wondering if we can/should be generating RunTests.sh.
• We could make this handle more samples, or similar projects too, but that doesn't have to be in this PR.
• In general, this looks fine, and it seems to work!
• It should be useful to get this in anyway, as it will prevent samples getting unintentionally broken.

[akoeplinger]

I'm wondering if we can/should be generating RunTests.sh

That is only done by the libraries tests afaik.

[safern]

That is only done by the libraries tests afaik.

This is done here. You could technically import these targets for the sample project and just hook them up:

runtime/eng/testing/tests.targets

Lines 51 to 52 in 93e767b

	<UsingTask TaskName="GenerateRunScript" AssemblyFile="$(InstallerTasksAssemblyPath)"/>
	<Target Name="GenerateRunScript">

I think I would rather do that and try to be consistent, it seems cumbersome to have that "workaround" in sendhelix to include the sample as part of the payload and hardcode the HelixCommand.

Can we open a follow up issue to clean this up and make it more generic for more samples? I see we also added this for iOS and it is doing somewhat similar instead of use the targets we already have.