Lazy container listeners

[AydinHassan]

• Only fetch container entries used for listeners when dispatching the event
• Add some methods + tests to ArrayObject + bring in Collection which is basically alias for ArrayObject as it looks weird using ArrayObject in the code when you want to use collection features.
• Move default event listeners to config and remove from the factory
• Migrate some tests to prophecy - so much nicer ❤️
• Change config structure for event listeners to allow grouping together events.

Eg

//before
[
    'some-event' => [
        'CoolFeature1Listener'
        'CoolFeature2Listener'
    ],
    'some-other-event' => [
        'CoolFeature1Listener',
    ]
]

//after
[
    'cool-feature1' => [
        'some-event' => [
            'CoolFeature1Listener'
        ],
        'some-other-event' => [
            'CoolFeature1Listener',
        ]
    ]
    'cool-feature2' => [
        'some-event' => [
            'CoolFeature2Listener'
        ],
    ],
]

[codecov-io]

Current coverage is 90.01% (diff: 100%)

Merging #138 into develop will increase coverage by 0.23%

@@            develop       #138   diff @@
==========================================
  Files            72         74     +2   
  Lines          1673       1713    +40   
  Methods         303        314    +11   
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits           1502       1542    +40   
  Misses          171        171          
  Partials          0          0          

Powered by Codecov. Last update f8510f3...622ff82

[mikeymike]

LGTM ... any reason to not just refactor the ArrayObject to Collection ? ... is it used outside of the lib?

[AydinHassan]

No but its used in some places as a wrapper for array as arrays arn't passed by ref. So it makes sense in that case. I'll have a think about it another time.