Currently there is no way to extend logic of DetectsLostConnections and DetectsConcurrencyErrors traits. The existing list of exception strings does not cover the list of all possible exceptions that may indicate a connection loss.

For example, we had an error Predis\Connection\ConnectionException with the text Connection timed out [tcp://1.2.3.4:6379] when working with predis and it did not resolved new addresses after redis node restart. Of course, traits do not provide exceptions for custom database and queues drivers. Therefore, the ability to extend their behavior may be required, but this is impossible while the logic is in the trait.

In this MR, the logic is transferred from traits to separate contracts and classes, which can then be extended by application users.

Changes are expected to be backward compatible with current version.
As far as this traits are used as a part of databaseManager, that can be used outside of laravel with Capsule, it tries to take detector from container, with fallback to default implementation