Avoid patch-package warning with 'npm install -g --production'

[pdcastro]

Fix the following warnings (result of PR #1739):

$ npm install -g --production balena-cli
...
Applying patches...
No patch files found
patch-package 6.2.2
Applying patches...
@oclif/[email protected] ✔
[email protected] ✔
[email protected] ✔

Warning: patch-package detected a patch file version mismatch

  Don't worry! This is probably fine. The patch was still applied
  successfully. Here's the deets:

  Patch file created for

    [email protected]

  applied to

    [email protected]

  At path

    node_modules/pkg

  This warning is just to give you a heads-up. There is a small chance of
  breakage even though the patch was applied successfully. Make sure the package
  still behaves like you expect (you wrote tests, right?) and then run

    patch-package pkg

  to update the version in the patch file name and make this warning go away.

qqjs/[email protected] ✔

Warning: patch-package detected a patch file version mismatch

  Don't worry! This is probably fine. The patch was still applied
  successfully. Here's the deets:

  Patch file created for

    [email protected]

  applied to

    [email protected]

  At path

    node_modules/qqjs

  This warning is just to give you a heads-up. There is a small chance of
  breakage even though the patch was applied successfully. Make sure the package
  still behaves like you expect (you wrote tests, right?) and then run

    patch-package qqjs

  to update the version in the patch file name and make this warning go away.

[email protected] ✔

Change-type: patch

[pdcastro]

My bad to have forgotten to add this line here. I had tested the release assets of PR #1739 (standalone zip packages, macOS installer, Windows installer) but I forgot to test npm install -g --production. Luckily the consequence is limited to the warning message during the installation.