Commit the composer.lock file

[ezzatron]

This PR does a few related things:

• Adds the composer.lock file. This is recommended by Composer, and should improve build times, and help when switching branches with different dependencies.
• Cleans up the .gitignore file, removing the composer.lock entry, and a bunch of entries that should really be in a global .gitignore file, such as .DS_Store and .idea.
• Uses slash prefixes in .gitignore where appropriate.
• Updates composer.json to use the platform config option, so that dependencies get locked at appropriate versions for our minimum PHP constraint.
• Updated dependencies to mitigate some Composer warnings about abandoned packages.

In regards to committing the lock file, there is the small downside that parallel changes to composer.lock always cause merge conflicts, but this is simple to fix, and the benefits outweigh the problems.

[codecov-io]

Current coverage is 96.74% (diff: 100%)

Merging #196 into master will not change coverage

@@             master       #196   diff @@
==========================================
  Files            20         20          
  Lines           645        645          
  Methods         162        162          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            624        624          
  Misses           21         21          
  Partials          0          0          

Powered by Codecov. Last update d04dfa4...f529ac4

[brianium]

@ezzatron - sounds good to me. I have rarely checked in lock files for these sort of projects, but I can't really think of a good reason why. Peridot is an application so 👍

I am super unfamiliar with the platform config - will this create issues with people using Peridot in a PHP 7 environment with newer deps? Our constraint is >= 5.4 so probably not right?

As for the .gitignore - I am not opposed to this. This would not be the first time I was called out on this. I just don't understand the need for it. Just good form? Keeps the .gitignore from bloating?

[ezzatron]

Re platform; it will change the dependencies that people who download a phar, or install globally, would get, because Composer will only choose dependencies that are compatible with PHP 5.4. I see this as a good thing though. You wouldn't want to globally install Peridot under PHP 7, then switch to PHP 5.4 and have it break suddenly.

For people who are bringing in Peridot under require-dev via Composer, the platform section is ignored, and they will get the latest deps possible. So it doesn't hold back those who are working exclusively with later versions of PHP.

There are some potential problems I suppose. The same kind of problems that arise with having ^2|^3 for our symfony/console constraint, in that we're only testing under CI with a sub-set of the dependencies that we support. The best way to fix that without going insane is probably to phase out support for older versions of PHP, and other dependencies, over time.

Re .gitinore, yeah, it's mostly to tackle bloat. It also means you don't have to duplicate this config across multiple repos, and it's easier to tell what transient files and directories are used by build processes and coverage reports without a bunch of cruft in there.

[ezzatron]

Awesome! I'll rebase the other branches off of this one ASAP.