chore: resolve JavaScript lint errors in utils/copy

[cskwork]

Summary

Fixes #11082

Resolves the stdlib/no-new-array lint error in the deep copy module by adding targeted eslint-disable-line comments where new Array(length) is intentionally required for sparse array preservation.

Changes

• lib/node_modules/@stdlib/utils/copy/lib/deep_copy.js (line 265): Added // eslint-disable-line stdlib/no-new-array
• lib/node_modules/@stdlib/utils/copy/lib/main.js (line 70): Added // eslint-disable-line stdlib/no-new-array

Rationale

new Array(x.length) cannot be replaced with [] because sparse array copies must preserve the .length property. The test suite explicitly verifies actual.length === 100 for sparse arrays. This pattern follows existing project precedent (e.g., @stdlib/stats/kstest/lib/main.js).

Test plan

• ESLint passes on both modified files

• Deep copy functionality verified: sparse arrays, nested arrays, standard objects all copy correctly

• Read, understood, and followed the contributing guidelines

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

[kgryte]

As the CI failure is not due to changes introduced in this PR, I'll go ahead and merge.

[stdlib-bot]

Coverage Report

No coverage information available.