useLiteralKeys rule should cover object properties

[Conaclos]

The useLiteralKeys lint rule reports code where static property access can be used instead of computed acces.

- a["b"]
+ a.b

This implements the EsLint dot-notation rule.

The EsLint no-useless-computed-key rule reports useless computed keys on an object literal:

{
-  ["b"]: 0,
-  ["1+1"]: 2,
-  ["f"]() {},
+  b: 0,
+  "1+1": 2,
+  f() {},
}

I suggest merging these two EsLint rule into useLiteralKeys.
The only minor inconsistency in the rule name is the simplification of ["1+1"] to "1+1".
The rule could also handle the following cases:

{
-  "b": 0,
- "f"() {},
+  b: 0,
+ "f"() {},
}

class C {
-  ["b"] = 0
-  "c" = 0
- ["f"]() {}
-  "g"() {}
+  b = 0
+  c = 0
+  f() {}
+  g() {}
}

This could also be done on interfaces and object types.

This is not a breaking change since useLiteralKeys is a nursery rule.

[ematipico]

Great suggestion!