Prevent APC causing random fatal errors [fixes #264]

Update the phar stub to prevent APC attempting to run the composer classes through the opcode cache on supported APC versions to avoid the random fatal "duplicate class" errors at runtime as reported in #264.

Prior to APC version 3.0.12 this was a PHP_INI_SYSTEM directive, so it outputs a warning instead.

I realise that there are existing recommended workarounds, either setting `apc.enable_cli = 0` (problematic if the user cache is required in CLI eg for functional/unit tests) or `apc.cache_by_default = 0` (requires global configuration and is hassle in environments when CLI and web configuration is otherwise the same).

I also realise that the fact APC is slowly on the way out, and the fact it can only be done with logic in the phar stub, means there are reasons not to accept this fix.

However, I do think it's worth doing - APC is still far from dead and the fatal error is not immediately obvious and happens semi-randomly with different classes. It's therefore hard to debug the first time you see it, and takes time to work out what's going on and update configuration to fix.

It would save a lot of head scratching and frustration if composer handled this internally where possible.
@stof indeed it does, but that doesn't help where the APC configuration is changed after composer is installed, or in environments where composer is installed by provisioning scripts. I'd never heard of the issue till I first got the fatal nor had others commenting on #264.