fix(transformer/typescript): retain TSImportEqualsDeclaration when it is exported

[Dunqing]

Related: #8458

While doing #8459, I found that I forgot to retain TSImportEqualsDeclaration when it's exported.

[Dunqing]

• fix(transformer/typescript): correct the semantic for TSImportEqualsDeclaration transformation #8463
• fix(transformer/typescript): retain TSImportEqualsDeclaration when it is exported #8460 👈 (View in Graphite)
• refactor(transformer/typescript): improve transforming namespace #8459
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Performance Report

Merging #8460 will not alter performance

_{Comparing 01-13-fix_transformer_typescript_retain_tsimportequalsdeclaration_when_it_is_exported (92283db) with 01-13-refactor_transformer_typescript_improve_transforming_namespace (779895c)}

Summary

✅ 29 untouched benchmarks

[graphite-app]

Merge activity

• Jan 14, 4:40 AM EST: A user added this pull request to the Graphite merge queue.
• Jan 14, 4:40 AM EST: The Graphite merge queue couldn't merge this PR because it had conflicts with the trunk branch.
• Jan 14, 5:55 AM EST: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Jan 14, 10:55 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.