feat(linter): typescript-eslint no-useless-empty-export

[keita-hino]

partof: #2180

docs: https://typescript-eslint.io/rules/no-useless-empty-export/
code: https://github.com/typescript-eslint/typescript-eslint/blob/584db29ec44ce4e9cb71afac35d48994889168e6/packages/eslint-plugin/src/rules/no-useless-empty-export.ts
test: https://github.com/typescript-eslint/typescript-eslint/blob/ac397f18176a9defd8c189b5b6b4e5d0b7582210/packages/eslint-plugin/tests/rules/no-useless-empty-export.test.ts

[codspeed-hq]

CodSpeed Performance Report

Merging #3605 will not alter performance

_{Comparing keita-hino:no-useless-empty-export (9dd7cb0) with keita-hino:no-useless-empty-export (790949f)}

Summary

✅ 22 untouched benchmarks

[Boshen]

I realized that we can just check if module record has empty exports when we see export {}.

This TypeScript case happens to rare, better to ignore it 😅

import _ = require('_');
export {};

[keita-hino]

@Boshen Thank you for the fix🙏