refactor(sqllab): nonblocking delete query editor

[justinpark]

SUMMARY

Following up #24539
This commit modifies the removeQueryEditor function to asynchronously handle the process of deleting a queryEditor in localStorage in the same way as in non-persistent mode and periodically post deleted items to persistence via AutoSync's deleteSqlEditor.

This commit made the following changes:

• In persistence mode, deleting a tab will no longer block the removal until it is fetched. Instead, the tab will be immediately discarded and stored the deleted ids in the local storage. (destroyedQueryEditors)
• removeQueryEditor has been modified to always update to localStorage in the same way as in non-persistence mode
• EditorAutoSync will execute deleteSqlEditor periodically and then remove the completed item from destroyedQueryEditors on success
• Add the logic of storing localStorage destroyedQueryEditors for persistence mode

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before:

before--nonblocking-close.mov

After:

after--nonblocking-close.mp4

TESTING INSTRUCTIONS

set SQLLAB_BACKEND_PERSISTENCE on
go to sqllab and then close each tab quickly

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[michael-s-molina]

Maybe use async/await here? I think it's more readable so feel free to apply the same pattern everywhere.

[justinpark]

This structure sends delete requests simultaneously, so if implemented with await, additional Promise.all handling might be required. Therefore, I intend to keep the current structure.