chore: fix JavaScript lint errors (issue #5377)

[suii2210]

Progresses #5377

Description
This pull request:

• replaces the obsolete sqrt precision script with a self-contained, lint-compliant version that uses @stdlib’s sqrt and avoids console log debug.

• Related Issues
  Progresses Tracking issue: Resolve JavaScript lint errors Tracking issue: Resolve JavaScript lint errors #5377

Checklist

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

[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 Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Gitter channel
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
math/base/special/sqrt	$\color{green}161/161$ $color{green}+100.00%$	$\color{green}4/4$ $color{green}+100.00%$	$\color{green}1/1$ $color{green}+100.00%$	$\color{green}161/161$ $color{green}+100.00%$

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

[suii2210]

I've updated the PR description to include the contributing guidelines acknowledgement.

[suii2210]

Hi maintainers - I updated the PR description and pushed a GPG-signed commit. Could someone please approve the workflow runs for this fork so CI can execute? Thanks!

[suii2210]

@stdlib-bot maintainers Could someone please approve the workflows and review this PR? Thanks!

[stdlib-bot]

⚠️ Tracking Issue Closure Warning ⚠️

I noticed your PR description contains closing keywords ("Resolves", "Closes", or "Fixes") referencing a "Tracking Issue".

Why this matters:
Tracking issues should typically remain open until all related sub-issues are completed. GitHub automatically closes issues with such closing keywords when the PR is merged. For more information, see GitHub's documentation on using keywords in issues and pull requests.

Required action:
Use "Progresses" instead to reference the tracking issue without automatically closing it.

Thank you for your contribution to the project!

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

[suii2210]

Hi @stdlib-bot - I’ve updated the PR description as requested (replaced “Resolves” with “Progresses” and added the contributing-guidelines acknowledgment).

Could you please re-check the PR and allow a maintainer to approve the workflow runs?
Thanks!

[kgryte]

Ref: #6433

@suii2210 Thank you for your interest in stdlib; however, the upstream issue was recently closed, as the referenced file was removed in a previous commit, thus rendering the lint issue and its resolution obsolete.

As such, I will go ahead and close this PR. Thank you for your interest in stdlib, and we look forward to your future contributions.