chore: fix JavaScript lint errors

[Sarfaraz604]

Resolves #9851

Description
What is the purpose of this pull request?

This pull request:

• Fixes JavaScript ESLint errors related to the stdlib/no-new-array rule and resolves file reference issues detected in the automated linting workflow
• Replaces 3 instances of new Array(100) constructor with array literals [] and .push() method initialization in the async inmap benchmark file
• Updates JSDoc example file references from foo.wasm to example.wasm to prevent linting errors on non-existent files

Related Issues
Does this pull request have any related issues?
No

Questions
Any questions for reviewers of this pull request?

No.

Other
Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist
Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

AI Assistance
When authoring the changes proposed in this PR, did you use any kind of AI assistance?

[ ] Yes
[x] No

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[SuYaSh-PaThAk04]

Please see the CI failure https://github.com/stdlib-js/stdlib/actions/runs/21246478250/job/61136933395?pr=9856.
examine this and resolve this .

[SuYaSh-PaThAk04]

Could you please double-check this change?we’re initializing the array iteratively—just want to ensure the length handling is correct and intentional here.

[Sarfaraz604]

ya checked

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
fs/read-wasm	$\color{green}259/259$ $\color{green}+100.00%$	$\color{green}28/28$ $\color{green}+100.00%$	$\color{green}3/3$ $\color{green}+100.00%$	$\color{green}259/259$ $\color{green}+100.00%$
utils/async/inmap	$\color{green}544/544$ $\color{green}+100.00%$	$\color{green}62/62$ $\color{green}+100.00%$	$\color{green}9/9$ $\color{green}+100.00%$	$\color{green}544/544$ $\color{green}+100.00%$

The above coverage report was generated for the changes in this PR.