Add lage to the benchmark

[kenotron]

Some context: https://twitter.com/kenneth_chau/status/1479591575512502273

1. added some nicety to handle windows pathing (.cmd shenanigans)
2. added lage
3. reduced the number of runs to 5 (50 took a long time, didn't see much variance)
4. made CONCURRENCY configurable as a constant
5. made the fix to the workspaces glob so it's not "unfair" to turbo

This benchmark is great! I made some changes to lage to make things run faster. I also am learning about the nx daemon advantages. It's really neat! I'm not sure how you can clean up background processes though.

[vsavkin]

Thank you for your PR! This is awesome.

I'll update the readme to include lage.

This benchmark is great! I made some changes to lage to make things run faster. I also am learning about the nx daemon advantages. It's really neat! I'm not sure how you can clean up background processes though.

The daemon helps us prep needed data structures.

• For Nx it matters more than for other tools cause Nx by default analyses not just package.json files but also js/ts files. This is to enable the creation of a more fine-grained project graph, where devs don't have to maintain package.json files unless they mean to publish those packages to a registry.
• Even with that capability, the daemon isn't really required. Nx caches stuff on disk, so it only incrementally reanalyses changed files, which is fast. However this process is pluggable, so while we can make this analysis fast, someone at a given org say adding support for .Net may not be as perf minded. Having the daemon gives those folks more room for how fast their plugins need to be.