refactor(transformer): construct new AST instead of calling ast.clone_in()

[Dunqing]

We should always avoid calling .clone_in because it will lose scoping information and it is not an efficient way. clone_in will traverse ast and calling clone_in for its all fields recursively

[Dunqing]

• refactor(transformer): construct new AST instead of calling ast.clone_in() #9916 👈 (View in Graphite)
• 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 Instrumentation Performance Report

Merging #9916 will not alter performance

_{Comparing 03-20-refactor_transformer_construct_new_ast_instead_of_calling_clone_in_for_original_ast (7f06cec) with main (30990d2)}

Summary

✅ 33 untouched benchmarks

[overlookmotel]

Merge activity

• Mar 21, 4:36 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 21, 4:36 AM EDT: A user added this pull request to the Graphite merge queue.
• Mar 21, 4:43 AM EDT: A user merged this pull request with the Graphite merge queue.