fix: allow chromium to handle WM_NCCALCSIZE for frameless windows

[deepak1556]

Description of Change

The event wasn't handled well for frameless window because of how we claim non client view with no system frame drawn https://cs.chromium.org/chromium/src/ui/views/win/hwnd_message_handler.cc?l=1421-1423

We handle it on our end #16596 but this has led to some perf regressions when maximizing and restoring windows, however if we provide the client area insets for frameless window, chromium can handle this event very well without us having to dedupe code paths.

Refs microsoft/vscode#84343, microsoft/vscode#81102

Verified not to regress the issues previously fixed by #16596, #18321, #19883, #19886, #19928

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: fix flickering when maximizing and restoring frameless windows

[zcbenz]

I have tested this PR under different combinations of window options and I can verify there is no regression.

The change looks good to me too.

[brenca]

LGTM! Nice catch!

[release-clerk]

Release Notes Persisted

fix flickering when maximizing and restoring frameless windows

[trop]

I was unable to backport this PR to "6-1-x" cleanly;
you will need to perform this backport manually.

[deepak1556]

The failing tests are not related to this PR, merging.

[trop]

I was unable to backport this PR to "7-1-x" cleanly;
you will need to perform this backport manually.

[trop]

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

[trop]

@deepak1556 has manually backported this PR to "7-1-x", please check out #21205

[trop]

@deepak1556 has manually backported this PR to "6-1-x", please check out #21206