INT-3458: Compatibility with Spring Framework 4.1

JIRA: https://jira.spring.io/browse/INT-3458

* Change Spring AMQP to `1.3.5.RELEASE`
* `HttpRequestHandlingEndpointSupport`: remove `MappingJacksonHttpMessageConverter` registration
* `IntegrationRequestMappingHandlerMapping`: add 'fake' `name()` attribute to the inline `RequestMapping` annotation
* `StoredProcJmxManagedBeanTests`: remove `context.stop();` code, Since `MBeanExporter` deregister MBeans on `stop()` now
* `StoredProcPollingChannelAdapterParserTests`: change deprecated `ParameterizedSingleColumnRowMapper` to the `SingleColumnRowMapper`
* `Jms`: comment out the reflection code to check the value for the `recoveryInterval`, because it is removed already in favor of `backOff`
* `NotificationListeningMessageProducer`: move the start-up listener registration to the `onApplicationEvent`,
because `MBeanExporter` moved `registerBeans()` to the `start()` now.
The same `phase` might cause the issue, that MBeans aren't registered yet for `NotificationListeningMessageProducer`
* `JpaOutboundGatewayTests`: change `@TransactionConfiguration` to the `@Transactional`. Don't know why the first doesn't work now.

**Cherry-pick to 4.0.x**
If the `this.listenerRegistered == true` from `start()`, that's great, because it means that we found our MBeans and listener for them.So `onApplicationEvent` should do nothing.
But `listenerRegistered` is `false`, because `this.retrieveMBeanNames()` returns **empty** `Collection` on `start()`, because `MBeanExporter` hasn't been started yet.
I can guess that there is some vulnerability, when some of MBeans are already, there, but some of them will be only after `MBeanExporter`. 
I'll change the code to postpone `isAutoStartup()` registration only to the `onApplicationEvent`.
But first of all you should convince me how `listenerRegistered == true`, if `objectNames.isEmpty()` :smile: