@typescript-eslint/no-namespace

[metreniuk]

Overview
Fixes the no-namespace rule for #503

Help needed

• I'm not sure how to better adjust the Tester to support running tests with different extensions, so I did the bare minimum and would appreciate guidance how to make it actually good. My current approach is just running a separate test/snapshot for tests that require a different extension. I was thinking adding it inside the options json, but it seemed unintuitive to use.
• I removed the guard around typescript declarations inside crates/oxc_semantic/src/builder.rs, but I'm not sure why it was in the first place.

Notes

• Added a typescript-eslint rule generator. Didn't support filename since had trouble adjusting the Tester module.

[Boshen]

We don't need to lint .d.ts because they are either machine generated or manually crafted.

[Boshen]

Since the namespace syntax works on ordinary TypeScript files, perhaps we don't need to change anything around filenames?

[metreniuk]

Since the namespace syntax works on ordinary TypeScript files, perhaps we don't need to change anything around filenames?

In the original rule there is an option allowDefinitionFiles that allows namespaces in d.ts, if we don't lint those I can just remove the option. Wdyt?

[Boshen]

Let's keep the parsed value and , we just don't use it for now.

Since the namespace syntax works on ordinary TypeScript files, perhaps we don't need to change anything around filenames?

In the original rule there is an option allowDefinitionFiles that allows namespaces in d.ts, if we don't lint those I can just remove the option. Wdyt?

Sounds good to me! Maybe keep the allowDefinitionFiles value in the code but comment out the relevant test cases?

[Boshen]

Thank you! Love the addition to rule gen!