variable-name generates naming-convention

[Benjamin Jones]

🐛 Bug Report

• tslint-to-eslint-config version: 2.10.0
• ESLint version: N/A
• Node version: v14.17.6

Actual Behavior

Running tslint-to-eslint-config on a tslint.json file with a variable-name rule, but no "check-format" option:

{
    "rules": {
        "variable-name": [true, "ban-keywords"]
    }
}

Outputs an .eslintrc.js file with a default naming-convention rule (without a selector).

{
    ...
    "rules": {
        "@typescript-eslint/naming-convention": "error",
        "id-denylist": [
            "error",
            "any",
            "Number",
            "number",
            "String",
            "string",
            "Boolean",
            "boolean",
            "Undefined",
            "undefined"
        ],
        "id-match": "error",
        "no-underscore-dangle": "error"
    }
}

Expected Behavior

I would expect this rule to only output the id-denylist rule, or at worst output a naming-convention rule with the variable selector as seems to be specified in the unit test.

Reproduction

Minimal reproducible example repo
Real life repo - Running eslint with a tslint-to-eslint-config-generated .eslintrc.js generates a ton of new naming-convention errors, which I think can be avoided.

[Benjamin Jones]

I'm curious if this is related to #1207 there seems to be some spooky action at a distance!