[FR] `"javascript/typescript.preferences.importModuleSpecifier": "no-relative-parent-imports"`

Works like https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-relative-parent-imports.md
The following patterns are considered problems:

/**
 *  in my-project/lib/a.js
 */

import bar from '../main' // Import parent file using a relative path

The following patterns are NOT considered problems:

/**
 *  in my-project/main.js
 */

import foo from 'foo' // Import package using module path
import a from './lib/a' // Import child file using relative path

/**
 *  in my-project/lib/a.js
 */

import b from './b' // Import sibling file using relative path

Start by reading the existing javascript/typescript.preferences.importModuleSpecifier setting and the examples in this issue. Trace where import-module-specifier preferences are defined and consumed, then add the no-relative-parent-imports behavior so parent-relative imports are rejected while package, child, and sibling imports remain valid. Done means the preference is supported and covered by the relevant existing tests.