chore: fix JavaScript lint errors (issue #11732)

[vedparkasharya]

Description

This PR fixes a JavaScript linting error reported in #11732.

Problem

The entries.js file in @stdlib/_tools/pkgs/entry-points/lib/ was using the new Array() constructor, which violates the stdlib/no-new-array ESLint rule.

Error:

lib/node_modules/@stdlib/_tools/pkgs/entry-points/lib/entries.js
  64:8  error  Using the `new Array()` constructor is not allowed; use an array literal with push instead  stdlib/no-new-array

Solution

Replaced new Array( total ) with an empty array literal [].

Before:

out = new Array( total );

After:

out = [];

Why this is correct

• The array is populated later via indexed assignment (out[i] = {...}), so JavaScript will automatically grow the array as needed.
• Using an array literal [] is the idiomatic JavaScript approach and satisfies the stdlib/no-new-array lint rule.
• No behavioral changes: the array still functions exactly the same way since subsequent code assigns elements by index.

Related Issues

resolves #11732

Checklist

• Read, understood, and followed the contributing guidelines

[kgryte]

Ref: #11736

[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.