Unify build version of helix extension

[cloudhan]

and basically style update to unify all build command to vsce from yarn as --follow-synlinks option is only support in vsce {package,publish,ls}

[cloudhan]

@71 This is what I used to produce #338 (comment)

Strackeror claim there is symlink issue on Windows, which is not the case. It can be fixed with group policy at least a decade ago, if not decades. See https://superuser.com/a/994147.
Since https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/ all you need to do is enable developer mode. Even a free llm chat give you correct answer in seconds.

[71]

This is no longer needed, but for future reference: please be kinder in future comments; "Even a free llm chat give you correct answer in seconds" is fairly hostile, especially since:

1. Modifying group policies and enabling developer mode is not necessarily possible for developers, e.g. in enterprise environments.
2. Even if it was, requiring system-wide changes to work on a VS Code extension is, IMO, too restrictive.

I do appreciate you investigating things, though!