Double Travis' PHP memory limit

[imjoehaines]

Goal

Travis is failing due to composer running out of memory when installing. This PR doubles the PHP memory limit, which still keeps us safely below the 7.5GB Travis has

This seems to have been exclusively affecting Laravel 5.1 on PHP 5 — Laravel 5.1. on PHP 7 installed fine and later versions of Laravel also worked on PHP 5

Review

For the submitter, initial self-review:

• [x] Commented on code changes inline explain the reasoning behind the approach
• [x] Reviewed the test cases added for completeness and possible points for discussion
• [ ] A changelog entry was added for the goal of this pull request
• [x] Check the scope of the changeset - is everything in the diff required for the pull request?
• This pull request is ready for:
  • [ ] Initial review of the intended approach, not yet feature complete
  • [ ] Structural review of the classes, functions, and properties modified
  • [x] Final review

For the pull request reviewer(s), this changeset has been reviewed for:

• [ ] Consistency across platforms for structures or concepts added or modified
• [ ] Consistency between the changeset and the goal stated above
• [ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
• [ ] Usage friction - is the proposed change in usage cumbersome or complicated?
• [ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
• [ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
• [ ] Thoroughness of added tests and any missing edge cases
• [ ] Idiomatic use of the language

[GrahamCampbell]

If composer is being very memory hungry, it is possible to enable the PHP garbage collector. It will make little but some different to memory usage, but will make composer ~4x slower... Which is why composer turns off the garbage collector before resolving dependencies.