chore(NA): assure puppeteer_skip_chromium_download is applied across every yarn install situation

[mistic]

We had a package.json config in order to skip the puppeteer local chromium download. However it appears it was only working for the general kbn bootstrap. That change will allow us to make it work also on our build process otherwise local chromium will be downloaded and we will experience the following error on macOS environment

 info [  kibana  ] Checking Windows for paths > 200 characters
   │ERROR failure 1 sec
   │ERROR Error: Windows has a path limit of 260 characters so we limit the length of paths in Kibana to 200 characters  and the following files exceed this limit:
   │       - node_modules/puppeteer/.local-chromium/mac-809590/chrome-mac/Chromium.app/Contents/Frameworks/Chromium Framework.framework/Helpers/Chromium Helper (Renderer).app/Contents/MacOS/Chromium Helper (Renderer)

[elasticmachine]

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

[spalger]

LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: bc63f78

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
enterpriseSearch	1.8MB	1.8MB	-51.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
upgradeAssistant	60.2KB	60.1KB	-51.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[mistic]

7.x/7.12: 049b45f
7.11/7.11.1: 1a7b475

[tsullivan]

I have found this issue while researching into using the "stock" chromium for MacOS and Windows, instead of doing a custom build. It looks like if we take the default approach to making that happen, then we would run into this bug again.