Delayed message consumption

[drmaciej]

Issue description

I'd like to touch on what was discussed in #125.

In short - can we have the listeners kick in only after the application has fully started, or as late in the process as possible? I've observed a few issues when writing tests and when running the application, whereby the listeners start processing messages before the application and all the beans have fully initialised. It would appear that AbstractJMSListenerMethodProcessor#registerListener is that piece that runs too early.

Can it be delayed in any way?