The script events `pre-archive-cmd` and `post-archive-cmd` can be used
to perform any tasks necessary when archiving the composer project.
This functionality can be used to run unit test or and other build
process before archiving, and can be used to distribute the archive
when completed
For one thing this wouldn't have worked for any custom installers anyway
which can write installed code to other places. This will now allow one
to use composer archive on a clean code checkout to build an archive as
we are used to. Or on one that had composer install run to build an
archive that can be used for deployment which includes the vendors.