fix: add uv_loop_close when object release to fix crash

[zuohuiyang]

Description of Change

stop_and_close_uv_loop add call uv_loop_close.
In the destructor of NodeBindings, stop_and_close_uv_loop is called, but stop_and_close_uv_loop does not call uv_loop_close. After NodeBindings are destructed, libuv still holds the member objects of NodeBindings. When power resume, libuv enumerates all loops, and will accesses a pointer that has been released.
as issue #32926

About npm test in checklist. Before I modified the code, 15 cases could not pass on my computer. After I modified, the failed cases did not increase, so there should be no problem with npm test.

Resolves #32926

Checklist

• PR description included and stakeholders cc'd
• npm test passes

Release Notes

Notes: Fixed crash in renderer when resuming system from sleep

[welcome]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉

[release-clerk]

Release Notes Persisted

Fixed crash in renderer when resuming system from sleep

[trop]

I have automatically backported this PR to "21-x-y", please check out #35336

[trop]

I have automatically backported this PR to "19-x-y", please check out #35337

[trop]

I have automatically backported this PR to "20-x-y", please check out #35338

[miniak]

/trop run backport-to 18-x-y

[trop]

The backport process for this PR has been manually initiated - sending your PR to 18-x-y!

[trop]

I have automatically backported this PR to "18-x-y", please check out #35340

[DanielMcAssey]

This seems to have broken in Mac with WebWorkers destructing. Will look at posting dump and repro