[Feature Request] Refactor Variable Removal Order to Prevent Compilation Errors During Development

Bug Description
when working with javascript/typescript, when deleting used variables, usually the removal happens in 2 steps:

1) the declaration/argument/parameter/property get's removed
2) the usage of the variable get's removed (could also be multiple steps, depending on how often the variable has been used

the issue with this is, that while developing, hot-reloading/refreshes of the app will crash the app interpretation because first the declaration get's deleted, which introduces errors, because the usage is still inside the code, the app is broken until all usage is cleaned up as well.

proposal: it would be nice if this process can be reversed, to first remove all the usage and as a last step, remove the declaration/argument/parameter/property, this way the refreshes would not break the app while the changes are processing

Environment Info

• Platform: darwin
• Terminal: zed
• Version: 1.0.111
• Feedback ID: c27686c7-73f0-41bc-a655-b260ca96356b