New rule: no-absolute-path

[jfmengels]

Based off this comment

This rule should forbid the use of imports with an absolute path. This is valid in Node.js, but should not appear in code in npm packages or in production, or better: never.

Invalid

import Foo from '/some/absolute/path.js';

Valid

import Foo from './some/relative/path.js';
import Foo from 'foo';

[benmosher]

I feel like I've already said this somewhere else (can't remember for sure), but what about no-absolute-path(s)?

[benmosher]

In the interest of pairing well with the plugin+/: import/no-absolute-path

[jfmengels]

👍 for import/no-absolute-path