fix: do not return value from Menu.setApplicationMenu

[tabishmahfuz1]

Description of Change

Closes #29088.

Fixed an issue where the void function Menu.setApplicationMenu would return a value on some platforms.

Checklist

• PR description included and stakeholders cc'd
• npm test passes(https://github.com/electron/clerk/blob/master/README.md#examples).

Release Notes

Notes: Fixed an issue where the void function Menu.setApplicationMenu would return a value on some platforms.

[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 an issue where the void function Menu.setApplicationMenu would return a value on some platforms.

[trop]

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

[trop]

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