When you run npm run build, it goes through all build:* tasks and processes them. This does not only trigger a fresh build (converting source files to build artifacts), but also triggers the packaging process (remove development dependencies and generate a ZIP archive).

As a follow-up to #3183, I'd like to decouple "building" from "packaging", so that npm run build only does the required steps to make the current source folder run as a valid plugin, and provide a separate npm run package (name up for debate) to optimize for a production environment and to generate a ZIP.

This seems to make sense, as an npm run build is something you need a lot during development, whereas you seldom need a ZIP file.

Related #3183, #1840