fix: crash in window.print()

[codebytere]

Description of Change

Closes #19687.

window.print() also calls InitPrintSettings and would not receive the settings received when we call webContents.print() so we need to send PrintHostMsg_GetDefaultPrintSettings over IPC in that case.

cc @jkleinsc @deepak1556

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• specs are 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: Fixed a crash in window.print().

[brenca]

LGTM!

[deepak1556]

Can you add a test for this, thanks! it can only be a basic api test but better to avoid situations where code path is accidentally removed.

[codebytere]

@deepak1556 the test itself passes but the native printer dialog pops when window.print() gets called and blocks so the tests time out every time. How would you suggest we proceed here?

The webContents.print() tests don't block since they don't invoke the dialog and can stay, but we may not be able to programmatically test window.print() itself.

[deepak1556]

Can you test with silent code path for window.print ?

[deepak1556]

LGTM since we can't UI test this without introducing testing apis in printing code.

[release-clerk]

Release Notes Persisted

Fixed a crash in window.print().

[trop]

I have automatically backported this PR to "7-0-x", please check out #19728