[RFC]: add an ESLint rule to disallow BigInt literal syntax

[kgryte]

Similar to https://github.com/nodejs/readable-stream/pull/542/files, the idea would be to add a new custom stdlib ESLint rule to disallow using BigInt literals (e.g., 1n).

This will be useful in advance of adding Int64 and Uint64 support for ndarrays, etc. There, we will always want to use constructors and treat the values as opaque objects, similar to stdlib's complex number objects.

This will help us maintain backward compatibility support and potentially allow polyfills.

Ref: https://github.com/stdlib-js/todo/issues/2356

Time estimate without AI: 5hrs
Time estimate with AI: 3-4hrs

[headlessNode]

@naterush I'm planning to work on this issue in the coming days. Could you please assign a label? Thanks!