[RFC]: create an ESLint rule to enforce that the last require in an example is a relative path

[Planeshifter]

In non-fixture example JavaScript files, typically, the last require statement should always be a relative require. E.g.,

// Bad...

var beep = require( '@stdlib/boop/beep' );
var foo = require( '@stdlib/bar/foo' );


// Good...

var beep = require( '@stdlib/boop/beep' );
var foo = require( './../lib' );

The reason for this practice is to make explicit that the API being demonstrated belongs to the respective package and also mitigates potential copy-paste bugs.

Time estimate without AI: 1h.
Time estimate with AI: 30min.

[Planeshifter]

PR-URL: stdlib-js/stdlib#5379

Loom recording:
https://www.loom.com/share/2334c3c92f514620b92421154f2e7197?sid=2e554e45-a961-4200-8046-ac3b2bf775d1

Time to completion: 45min

Time after initial review: 10min.

[Planeshifter]

Notes:
Cursor wrote a correct implementation immediately and scaffolded out the files for me. It didn't add license comments (even though Composer did it for a previous PR), so I had to add these manually. I also changed the implementation to not check for whether the file resides in an examples directory, as we have ESLint setup such that we can apply different configurations for benchmarks, examples, and source code. But that is context that wasn't specified in the issue. Finally, I missed that the package.json file wasn't generated, so had to do some debugging in the end when enabling the rule. Overall great experience!