chore: fix JavaScript lint errors (issue #9015)

[manit2004]

Resolves #9015

Description

What is the purpose of this pull request?

• Fixes two JavaScript linting errors detected in the automated lint workflow
• Moves the copyLocationInfo function to module scope in lib/node_modules/@stdlib/_tools/eslint/rules/jsdoc-no-heading-punctuation/lib/main.js to comply with the stdlib/no-unnecessary-nested-functions rule
• Removes extra space before closing parenthesis at line line 33 and 34 in lib/node_modules/@stdlib/console/log/examples/index.js to comply with the stdlib/line-closing-bracket-spacing rule

This pull request:

This pull request has the following related issues:

• Resolves Fix JavaScript lint errors #9015

Related Issues

Does this pull request have any related issues?

• No

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.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

---

@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
console/log	$\color{green}92/92$ $\color{green}+0.00%$	$\color{green}3/3$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}92/92$ $\color{green}+0.00%$

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

[kgryte]

LGTM

[kgryte]

Thank you for your contribution and congratulations on your first PR!

[manit2004]

Thanks.