ModuleEntryInterceptor sitting before the async invocation interceptor causes traces to place spans in the wrong place

[odrotbohm]

ModuleTracingBeanPostProcessor always registers the interceptor as first in the advisor chain. If the AsyncAnnotationAdvisor is already present, this will cause close to empty spans for async event listeners as the span starts before the async dispatch and immediately ends.