chore: use concurrently for the build process

[kmruiz]

Proposed changes

concurrently allows running independent tasks in parallel in different node.js processes. This can reduce execution time drastically. In my machine it reduces the npm run check command execution time to a half.

Without concurrently:
real	0m20.025s
user	0m41.886s
sys	0m1.882s

With concurrently:
real	0m9.910s
user	0m59.061s
sys	0m2.201s

In GHA, it reduces around 40s the check step (25% faster).

Checklist

• I have signed the MongoDB CLA

[Copilot]

Pull Request Overview

This PR introduces concurrently to parallelize independent build and check tasks, reducing execution time by approximately 50% (from ~20s to ~10s on the author's machine). The change optimizes the development workflow by running tasks that don't depend on each other simultaneously.

Key Changes

• Consolidated the build:chmod command into build:esm by chaining it with &&
• Modified the build script to run ESM, CJS, and universal package builds in parallel using concurrently
• Modified the check script to run build, type checking, linting, formatting, and dependency checks in parallel

[coveralls]

Pull Request Test Coverage Report for Build 18721059018

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 79.906%

---

Totals
Change from base Build 18717167438:	0.0%
Covered Lines:	6143
Relevant Lines:	7557

---

💛 - Coveralls

[gagik]

Nice, seems like the reason this works without changing our deps is because @modelcontextprotocol/inspector uses it, should we have concurrently as an explicit dev dependency?

[kmruiz]

Nice, seems like the reason this works without changing our deps is because @modelcontextprotocol/inspector uses it, should we have concurrently as an explicit dev dependency?

Yeah, it's weird that npm i -D didn't add the dependency. I've added it manually and pushed the changes. Thanks for noticing it!