chore: add logging for print_backend failures

[codebytere]

Description of Change

Refs:

• https://chromium-review.googlesource.com/c/chromium/src/+/2796126
• https://chromium-review.googlesource.com/c/chromium/src/+/2932396

Chromium recently added the ability to distinguish between no printer(s) and a query failure. I don't think a failure to enumerate printers should result in a user-facing error, but we should at least log this nuance instead of dropping it on the ground.

Checklist

• PR description included and stakeholders cc'd
• 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: none

[deepak1556]

We propagate user facing generic error on failure cases of obtaining a valid printer

electron/shell/browser/api/electron_api_web_contents.cc

Lines 2369 to 2373 in 2131992

	if (printer_name.empty() || !IsDeviceNameValid(printer_name)) {
	if (print_callback)
	std::move(print_callback).Run(false, "no valid printers available");
	return;
	}

If we want to distinguish the failures further, shouldn't they be added to final user facing error message ?

[deepak1556]

LGTM in general

[deepak1556]

Looks like linux arm DCHECK crashes are related.

[codebytere]

@deepak1556 yeah i'm seeing:

[88155:0908/214127.957025:ERROR:print_backend_cups.cc(218)] CUPS: Error getting default printer: Bad file descriptor

is this something you think we should try to fix ourselves or just not run this specific test there given it was already not succeeding?

Ah wait i missed this was a crash and not just a failure - hmmmm i'll look into it though it's slightly baffling given that this isn't really a behavioral change in terms of Chromium functions being called.

[deepak1556]

Looks like the DCHECK fails once the print backend mojom has a failure (not sure why the scoped_refptr referencing the backend would fail at this point), might want to try emulating the mojom failure locally and see if it repros.

[release-clerk]

No Release Notes

[trop]

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

[trop]

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

[trop]

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