build: fix line reporting for no-empty-lines-between-requires lint rule

[Planeshifter]

Resolves stdlib-js/metr-issue-tracker#153.

Description

What is the purpose of this pull request?

This pull request:

• changes the no-empty-lines-between-requires ESLint rule to report errors on the first require statement after the empty lines, rather than on the empty lines themselves
• enables targeted suppression via // eslint-disable-line stdlib/no-empty-lines-between-requires
• adds a test case verifying that inline disable comments work

Previously, the rule reported errors with node: null and a synthetic loc pointing at the blank lines between require statements. Since blank lines contain no code, // eslint-disable-line comments could not be placed there, making per-line suppression impossible. The only workaround was disabling the rule for the entire file.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [BUG]: fix line location in no-empty-lines-between-requires rule metr-issue-tracker#153
• chore: fix JavaScript lint errors (issue #9527) #9530 (comment)

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.

The key change in context.report():

- context.report({
-     'node': null,
-     'message': 'Unexpected empty line between require statements.',
-     'loc': loc,
-     'fix': fix
- });
+ context.report({
+     'node': currNode,
+     'message': 'Unexpected empty line between require statements.',
+     'fix': fix
+ });

By reporting on currNode (the require statement after the gap), ESLint uses that node's location. Users can now append // eslint-disable-line stdlib/no-empty-lines-between-requires to suppress the rule on that specific line.

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

This PR was written primarily by Claude Code under my direction.

---

@stdlib-js/reviewers