Rule merger for @typescript-eslint/ban-types should deeply merge objects

[JoshuaKGoldberg]

Overview

@typescript-eslint/ban-types has a fixWith option for types. https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/ban-types.md

Actual Behavior

That fixWith might go away if two rule arguments types lists are merged and the second doesn't have it.

First:

{
  types: [
    {
      fixWith: "number",
      typeName: "Number",
    },
  ];
}

Second:

{
  types: [
    {
      typeName: "Number",
    },
  ];
}

Output:

{
  types: [
    {
      typeName: "Number",
    },
  ];
}

Expected Behavior

The output should include fixWith if it exists.

[Res42]

Also another issue with this merger: when merging a configuration with no-args and a configuration which only contains types that are included in the default options (with no-args) it should merge these to no-args since that is "stronger".

The default types configuration is here: https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/ban-types.md