[Tests] named: Add direct test for export = assignment in TS

[ProdigySim]

This pattern is valid typescript, but import/named can't find resolve the imports. Relevant issue: #1984

Here's a demo showing that it should work in TS

Test fails with

  1) TypeScript named [TypeScript] valid import { FooBar } from './typescript-export-assign-object':

      AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: Should have no errors but had 1: [
  {
    ruleId: 'named [TypeScript]',
    severity: 1,
    message: "FooBar not found in './typescript-export-assign-object'",
    line: 1,
    column: 10,
    nodeType: 'Identifier',
    endLine: 1,
    endColumn: 16
  }
]
      + expected - actual

      -1
      +0

Reopened from #2428

[codecov]

Codecov Report

Merging #2432 (a8781f7) into main (116af31) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2432   +/-   ##
=======================================
  Coverage   95.17%   95.17%           
=======================================
  Files          66       66           
  Lines        2799     2799           
  Branches      940      940           
=======================================
  Hits         2664     2664           
  Misses        135      135           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ljharb]

I've rebased this, and looking over it, it's actually correct - export = syntax creates only a default export, at least when esModuleInterop is on (without which, TS's module system is broken anyways). You can't named-import from a module that uses that.