fix: resolve JavaScript lint errors (no-error-string-concat, no-new-array)

[sputnik-mac]

Description

Fixes two JavaScript lint errors caught in the automated lint workflow (issue #10556).

Changes

1. lib/node_modules/@stdlib/utils/async/for-each-right/examples/index.js

• Replaced string concatenation in error message with @stdlib/string/format
• Fixes: stdlib/no-error-string-concat lint error at line 45

2. lib/node_modules/@stdlib/math/strided/special/ahavercos-by/test/test.ndarray.js

• Replaced new Array( 5 ) constructor calls with Array.from( { 'length': 5 } )
• Fixes: stdlib/no-new-array lint errors at lines 76 and 84

Checklist

• Code follows stdlib conventions
• Fixes lint errors referenced in Fix JavaScript lint errors #10556
• No functional changes — behavior is preserved

Closes #10556

[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

[kgryte]

Ref: #10557

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.