src, child_process: fix fatal error on Array prototype pollution

[Soumyadeep765]

Add an object check in ParseStdioOptions to prevent V8 from crashing with "v8::ToLocalChecked Empty MaybeLocal" when Array.prototype has been polluted. This replaces the fatal error with a controlled JavaScript TypeError (ERR_INVALID_ARG_TYPE).

Fixes: #56531

Assisted-by: Antigravity

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

[MikeMcC399]

This PR proposes a fix for #56531 which has the label good first issue Issues that are suitable for first-time contributors. attached.

AI use policy and guidelines says:

It's prohibited to use AI to automate fixes to issues marked as "good first issue". These issues are meant to help new human contributors, not an AI, learn about the code base and the contribution processes.

Soumyadeep765@a329954 however contains the following text which suggests that AI was used to automate the fix:

Signed-off-by: soumyadeep765 soumyadeepdas765@gmail.com
Assisted-by: Antigravity

The PR has not followed the Pull Request guide which advises to create a local branch, as described in Step 2: Branch. Changes have been made in the fork's main branch.

See Pull requests > Step 6: Test

Before submitting your changes in a pull request, always run the full Node.js test suite.

with further details under [BUILDING > Running tests](Running tests) including:

make lint/ vcbuild lint for linting only.