feat: use generic package manager

[royalgarter]

This change is 

---

- For better compatible with project using npm only
- Tested with node 18/20/22 (npm 10+)

Add support to package managers (not only yarn or npm):

• yarn
• npm
• others (pnpm etc)

TODO:

• Update README

Fix #1543

[xTudoS]

Just a question. There will be no need to add a package-lock.json or a something similar to that to keep packages versions synced?

[rtritto]

I should use (prefer) yarn as main package manager because it use some fields in package.json and has some additional files.
To sync (freeze) dependencies we can use yarn.lock. Imo maintain the package-lock.json too isn't needed.
At install step, each package manager removes files of other package managers and creates files that it needs.

[rtritto]

@BlackthornYugen what do you think about this changes?

[BlackthornYugen]

I'm not familiar with the cross-env, but I would agree that package locks are required so that we can have reproducible builds.

[rtritto]

So we must maintain and update both yarn.lock and package-lock.json files.
For instance, we can use a preinstall script, that use logics based on package manager used (imo we need to move the other (not related) lock files to a temporary folder).

We need some ideas 🤔

Imo this feature can be merged and the maintain lock files will be handled in another feature.

P.S.: next we can also add the pnpm support.

[rtritto]

For the feature that update (handle) lock files, I created this WIP https://github.com/mongo-express/mongo-express/tree/update-lock-files

Can anyone review this PR?