DevKit updates for 3.x branch

[SonataCI]

No description provided.

[greg0ire]

@makasim can you help with the Travis build? You introduced a deprecation for getChannel, but did not migrate code in src/Backend/AMQPBackend.php, and it still calls the deprecated method, which means our users are probably getting unfixable deprecations.

[makasim]

The master shouldn't use the deprecated code.

[greg0ire]

This is 3.x

[OskarStark]

@makasim can you support us here?

Testing Sonata Notification Bundle Test Suite
................................................................. 65 / 78 ( 83%)
.............                                                     78 / 78 (100%)
Time: 7.51 seconds, Memory: 42.00MB
OK (78 tests, 233 assertions)
Generating code coverage report in Clover XML format ... done
Remaining deprecation notices (2)
The Sonata\NotificationBundle\Backend\AMQPBackendDispatcher::getChannel method is deprecated (since 3.2, will be removed in 4.x): 2x
    1x in AMQPBackendTest::testGetIteratorWithPrefetchCount from Sonata\NotificationBundle\Tests\Backend
    1x in AMQPBackendTest::testGetIteratorWithNoPrefetchCount from Sonata\NotificationBundle\Tests\Backend
make: *** [test] Error 1

[makasim]

Nothing to do with 3.x branch. It uses deprecated stuff. Master does not rely on it any more

[OskarStark]

@greg0ire the weird part here is, that the other builds succeed... 🤔

[greg0ire]

Nothing to do with 3.x branch. It uses deprecated stuff. Master does not rely on it any more

That's my point, 3.x can expose deprecated stuff, but shouldn't use it, people should be able to migrate to "the new way" in 3.x and get rid of the deprecations without upgrading to 4.0 (which they cannot for now)

[makasim]

@greg0ire @OskarStark see #341

[greg0ire]

Finally :)