Fixing test p5.js web

[Jatin24062005]

Issue:

Fixes #3978

Demo:

Changes

1. Added cross-env to scripts for consistent environment variable handling across platforms.
2. Removed the explicit MongoDB version from MongoMemoryServer.create() to avoid timeout errors and repeated binary downloads during tests.

Why

• cross-env ensures scripts run correctly on Windows, macOS, and Linux.
• Dropping the pinned MongoDB version prevents Jest hooks from stalling while fetching unsupported or slow binaries.

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• has no typecheck errors (npm run typecheck)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123
• meets the standards outlined in the accessibility guidelines

[Jatin24062005]

after making test run it's giving some Component mounting error !

[Jatin24062005]

Hi @clairep94 @raclim, I’ve cleaned up the test suite to improve our signal-to-noise ratio, ensuring npm run test now produces a clean, actionable output. I updated the Jest setup to specifically suppress the persistent Route prop-type errors and legacy lifecycle warnings (like componentWillUpdate in the Editor) that were cluttering the logs. This eliminates "warning fatigue," ensuring any new regressions stand out immediately rather than being buried.
I also addressed the Mongoose duplicate index warnings we discussed in the previous issue to further declutter the server logs #3752 .
Ready for review & merge!

[Jatin24062005]