import-blacklist: allow package name preferences?

[JoshuaKGoldberg]

(forking from microsoft/tslint-microsoft-contrib#422)

When there are two modules that declare variables with the same name, it's easy to mistakenly import from the wrong package:

import { action } from "mobx"; // this one?
import { action } from "mobx-safe"; // or this one?

A rule that lets projects map imports to their preferred package imports would help:

{
    "rules": {
        "import-blacklist": [
            true,
            "rxjs",
            {
                "mobx-safe": {
                    "action": {
                        "override": ["*"],
                        "reason": ["Technical mumbo jumbo..."]
                    }
                }
            }
        ]
    }
}

...though this config could be misleading, as the "rxjs" setting tends away from that module while "mobx-safe"'s tends towards that one. I'm not sure if I have a preference to add to import-blacklist or make a new rule.

[ethanresnick]

@JoshuaKGoldberg Would my PR here address your use case? #3926

[JoshuaKGoldberg]

Looks like it!

[JoshuaKGoldberg]

Fixed by #3926 🙌