Starting the Update process
Update step 1 - Fetch package
Tweaks to apply update CLI
Extract package step built
Merge branch 'master' of bitbucket.org:allyde/mautic into WebUpdates
Ignore the upgrade directory, it is a temp directory only used for upgrades
Initial batch of code for the standalone portion of the updater

Included here:
- Outline of all move file steps and resource functions to accomplish these tasks
- Base framework for receiving requests from main Mautic app, processing them, and sending data back into the main app
- Support for a basic error log; right now it just spits out messages about what could not be created/copied
- Initial code for moving all of the bundles from the temp upgrade extract into the production filesystem
Just inject the state at the beginning and forward it along
Some refinements after initial testing
Merge branch 'master' of bitbucket.org:allyde/mautic into WebUpdates
Refining the packaging scripts, now the release script uses a git tag
Fill in the remove_mautic_deleted_files function
Stop repeating error log handler
copy_directory will move the files
Move the rest of Mautic core
Flag if the dependencies changed
Moving vendors and clearing cache, CLI updater processes deleted files
Database migration step
FilesystemIterator doesn't have the isDot method!?
Update prod assets