fix(linter/no-promise-executor-return): check if Promise is the global one

[camchenry]

Previously we only checked if the identifier was called Promise. Now, we also check if it's the global reference or a locally bound reference.

[camchenry]

• fix(linter/prefer-destructuring): fix rule to exclude using and await using #17952
• feat(linter/no-useless-rename): add automatic fix #17951
• fix(linter/no-promise-executor-return): check if Promise is the global one #17949 👈 (View in Graphite)
• fix(linter/no-await-in-loop): add support for await using #17947
• 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]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 41 skipped benchmarks¹

---

_{Comparing 01-12-fix_lintr_no-promise-executor-return_check_if_promise_is_the_global_one (f0fec5d) with 01-12-fix_linter_no-await-in-loop_add_support_for_await_using_ (088e6c1)}

Footnotes

1. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[camc314]

Merge activity

• Jan 14, 11:41 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 14, 11:42 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Jan 14, 11:52 AM UTC: Merged by the Graphite merge queue.