Should we provide a config that disables some rules from `@typescript-eslint/eslint-plugin`?

For example, no-use-before-define is often wrong if you define multiple components in the same file.

```gjs
const Foo = ;
const Bar = hi;
```

would trigger the error.
But this is totally valid, because component rendering is not _eager_ like const-evaluation normally is.

cc @patricklx, in case you have ideas

example in vanilla: