fix: prevent navigator.fonts.query() from crashing

[codebytere]

Description of Change

Closes #30884.

Follow-up at #30932.

Fixes a crash in navigator.fonts.query(). Chromium relies on a user choice via a UI they pop up to run the callback, and in contrast we don't really have a way to run the closure post-construction of the FontAccessChooser and therefore must run it in the constructor, which makes it such that FontAccessManagerImpl::DidChooseLocalFonts runs before the FontAccessChooser is assigned in the choosers_ map and DCHECKS.

As we don't yet have a standardized permissions model for this and similar APIs, this just mediates the crash and adds appropriate simple scaffolding for a proper implementation.

Tested with https://gist.github.com/bbae1d3b31214682fb6a05ec69b5d97a.

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: Fixed a crash in navigator.fonts.query().

[release-clerk]

Release Notes Persisted

Fixed a crash in navigator.fonts.query().

[trop]

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

[trop]

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

[nornagon]

It seems like you could probably pass std::move(close_callback) here rather than re-wrapping it, yes? i.e.

Suggested change

	base::PostTask(
	FROM_HERE, {content::BrowserThread::UI},
	base::BindOnce(
	[](base::OnceClosure closure) { std::move(closure).Run(); },
	std::move(close_callback)));
	base::PostTask(FROM_HERE, {content::BrowserThread::UI}, std::move(close_callback));

[gpetrov]

Please backport to Electron 13 as well @codebytere