Match MKC and include test files when sharing projects

[aznhassan]

Problem

Sharing a project with testFiles in its pxt.json in the extension will result in a shared project that does not load. This happens because the test files are excluded from the text sent to the backend but still left in the pxt.json. When the project is loaded in a browser, the typescript compiler will fail since the missing test file will be null.

Solution

Use MKC

One possible solution is to just use the makecode package directly. However, the makecode package does some extra work around downloading and caching the target editor before sharing the project. This is probably the reason we chose to just match the rest of the sharing logic instead of using it directly.

Even if we wanted to just use the makecode extension, the exposed shareCommand that we would use returns void and merely logs the link to the console. So, we'd have to update MKC instead of just using it as a drop-in replacement of the already existing shareLink.ts

Match MKC and include test files

The makecode package will include the test files in the shared project if they are present. We can just match that behavior to fix the issue.

Validation

I created a local vsix and installed it. I cloned https://github.com/Kikketer/arcade-testshare locally and opened the folder in new VS Code Window. Using the extension, I was able to share the project. It now loads as expected. https://arcade.makecode.com/85698-69144-34682-34885

fixes #7278

[jwunderl]

LGTM (did you figure out what the problems were with vsix / run in web scenarios?)

[aznhassan]

LGTM (did you figure out what the problems were with vsix / run in web scenarios?)

Yup! Richard helped me out; turns out it was a WSL issue. What exactly? I'm not sure, but it worked as expected once I installed the VSIX from Windows.