[Screenshotting] Diagnostic tool gives false positive on "Fontconfig error: No writable cache directories"

[pmuellr]

We're seeing a new error not caught by the Screenshotting diagnostics tool. The following messages are logged when system fonts are not installed:

Fontconfig error: No writable cache directories

Previous attempts at catching errors like these: #186434

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[petrklapka]

@pmuellr - We are going to bow out of this one Pat. Please triage on your team. Let us know if you need a hand!

[pmuellr]

Thinking we can change the code here to just look for Fontconfig error: rather than a specific Fontconfig message

kibana/x-pack/platform/plugins/private/reporting/server/routes/internal/diagnostic/browser.ts

Lines 38 to 44 in 9dc67bf

	'Fontconfig error: Cannot load default config file': i18n.translate(
	'xpack.reporting.diagnostic.fontconfigError',
	{
	defaultMessage: `The browser couldn't start properly due to missing system font dependencies. Please see {url}`,
	values: { url: docLinks.links.reporting.browserSystemDependencies },
	}
	),