chore: fix JavaScript lint errors (issue #7728)

[siddhesh434]

Resolves #7728.

Description

What is the purpose of this pull request?

This pull request:

• Fixes JavaScript linting errors detected during the GitHub Actions lint workflow run (link).
• Specifically resolves the following ESLint error in the file:
  • lib/node_modules/@stdlib/stats/base/dists/bernoulli/ctor/lib/main.js:
    • JSDoc return annotation updated from // returns 1 to // returns 1.0 to follow the required decimal point format for number values.

This change is part of a broader effort to clean up JavaScript lint violations across the codebase, tracked in issue #5377.

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves #7728

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.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[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
stats/base/dists/bernoulli/ctor	$\color{green}409/409$ $\color{green}+100.00\%$	$\color{green}26/26$ $\color{green}+100.00\%$	$\color{green}15/15$ $\color{green}+100.00\%$	$\color{green}409/409$ $\color{green}+100.00\%$

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