fix: broken wayland window decorations due to botched chromium update

[msizanoen1]

Description of Change

The GetTitlebarBounds().height() expression is obviously intended to be placed in the top parameter, which used to be the second one before upstream removed multi-parameter gfx::Rect::Inset, but it's the first parameter for gfx::Insets::TLBR, which was intended to replace the removed Inset function. However, whoever updated Chromium kept the parameter ordering unchanged, causing the title bar height to be passed to the left parameter, causing the window title bar to be unclickable.

Fixes partially #34820

Checklist

• PR description included and stakeholders cc'd (@refi64)
• npm test passes
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fix mangled Wayland client-side decorations

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

[deepak1556]

Thanks!

[refi64]

Thanks for looking into this!

[ckerr]

This is a nice fix and is approved, but I'm going to close it since @msizanoen1 has marked it as superseded by #34955 and the PR there does include this fix. So let's continue discussion over in that PR