feat: Added Browser Window Click Event (Issue #24351)

[chrisssz]

Description of Change

Added Browser Window Click Events

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• [ x] relevant documentation, tutorials, templates and examples are changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: none

[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.

[codebytere]

Can you please say a little more about your goals here? I see you're trying to address #24351 but this PR has no documentation, no tests, and no end-user API exposure.

At the moment, it also doesn't compile as it's not been fully or correctly implemented. We're happy to try to help resolve the issue, but we can't really proceed with review in this state.