[11.x] Configuration to disable events on Cache Repository

[serpentblade]

This change allows caches to be defined without auto-registering events dispatcher.

On in-memory caches like array or apc, the overhead of triggering events results in an 80%+ overhead for basic cache operations. This change allows a config value on any cache definition to disable events for that particular Repository.

Benefit:
In some circumstances it is helpful to use an in-memory cache like array or apc, however in operations that use a lot of cache calls the overhead starts to dramatically impact performance. Being able to define a cache without events allows for the conveniences of the caching API while minimizing the overhead to the API implementation and not the events side-effects.

Usage:
Adding 'with_events' => false to any cache stores configuration will prevent the automatic registration of the events dispatcher. For example, the following changes the 'array' store to not register events:

[
    ...
    'stores' => [
        'array' => [
            'driver' => 'array',
            'serialize' => false,
            'with_events' => false,
        ],
   ]
]

Backwards Compatibility Concerns:
I've implemented this new setting to default to true when the setting isn't defined on the config, so it has no backwards compatibility concerns.

Tests:
Added test for CacheManager to handle this new setting and test the previous functionality where no setting is provided.