Do not use the {} type to represent an empty object as representing any non-nullish value

[danielwiehl]

Describe the bug

@typescript-eslint bans {} as type because it does not represent an empty object as most developers would expect, but "any non-nullish value" instead. As a workaround, we disabled the linting rule @typescript-eslint/ban-types to not report a violation for {} types.

Expected behavior

We do not use the {} type to represent an empty object and have re-enabled the linting rule @typescript-eslint/ban-types.

See the following links for more information:

• https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/ban-types.md
• [ban-types] Should not ban {} by default! typescript-eslint/typescript-eslint#2063 (comment)