Reporting causes a fatal Kibana error if chromium is not installed on aarch64

[liza-mae]

Kibana version: 7.11.0 BC 1

Elasticsearch version: 7.11.0 BC 1

Server OS version: Ubuntu aarch64

Browser version: Chrome Latest

Original install method (e.g. download page, yum, from source, etc.):
staging

Description of the problem including expected versus actual behavior:
Running reporting without chromium causes Kibana fatal error, it's a regression from 7.10.1.

Steps to reproduce:

1. Install ES/Kibana
2. Run reporting on a machine without chromium installed, Kibana aborts.

{"type":"log","@timestamp":"2021-01-04T01:48:28+00:00","tags":["info","plugins","reporting","printable_pdf","execute-job","kjhwnaqz0bj61249e24tsnt5","kjhwnaqz0bj61249e24tsnt5","browser-driver"],"pid":14946,"message":"Creating browser page driver"}
Error: spawn /usr/bin/chromium-browser ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[tsullivan]

The bug here is that the puppeteer module thinks that it should use a system-wide Chromium instead of the custom build shipped with Kibana.

The relevant PR here is probably: #85066 I seem to remember there was some trial-and-error to get the puppeteer module to load our own custom build. Perhaps there is separate work to do for aarch64?

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[tylersmalley]

@tsullivan, I found the issue - the path is hardcoded for arm: https://github.com/puppeteer/puppeteer/blob/main/src/node/Launcher.ts#L107

This has been raised here: puppeteer/puppeteer#6614

[tylersmalley]

Sync'd with Tim and Brandon - there is a PR open for a fix which I have confirmed. I will create a fork that we can use in the meantime to unblock the release.