fix(npm-scripts): support windows platform using cross-var

[llc1123]

Which problem is this PR solving?

Currently, the project cannot run on Windows because the npm script:

"precompile": "lerna run version --scope $(npm pkg get name) --include-dependencies"

Windows doesn't support inline shell scripts like this.
But we can use npm_package_name env var instead.
But Linux/macOS uses $ style env var references while Windows uses %% style.

Short description of the changes

• Added cross-var as a devDependency and modified the npm script to support Windows.
• Also fixed some minor issues. (packages missing pre-scripts).

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Run npm run compile on Windows machines.

Checklist:

• Followed the style guidelines of this project

[codecov]

Codecov Report

Merging #3857 (bd643fb) into main (228e67b) will decrease coverage by 0.02%.
The diff coverage is n/a.

❗ Current head bd643fb differs from pull request most recent head 049ffa5. Consider uploading reports for the commit 049ffa5 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3857      +/-   ##
==========================================
- Coverage   92.98%   92.97%   -0.02%     
==========================================
  Files         300      300              
  Lines        9104     9104              
  Branches     1862     1862              
==========================================
- Hits         8465     8464       -1     
- Misses        639      640       +1     

see 1 file with indirect coverage changes

[Flarna]

In contrib repo we directly used the package name instead of $(npm pkg get name), see e.g. here

But more general I wonder why there are still compile and precompile scripts in each package because the actual build is done meanwhile by a typescript project in root. The compile task in root project doesn't delegate to subprojects anymore (see here).

Maybe we should just remove these npm scripts?

[llc1123]

But more general I wonder why there are still compile and precompile scripts in each package

If you want to just compile one package and its dependency, you can just go under the package directory and run npm run compile, especially when dependency compilation is required for the tests.

[llc1123]

In contrib repo we directly used the package name instead of $(npm pkg get name)

Either using env var or hard code the package name is okay.