Camel tracer with stream caching should tracer after stream cache has been setup

When using tracer then it may run before stream caching gets kicked-in, which means the tracer may read the input stream causing the stream to not be re-readable by the stream caching, and therefore cause it to be empty.

This only happens if you turn on stream cache bodies on the tracer, which is off by default. And if the input message is stream based that is no re-readable by itself.

We should ensure the stream caching advice is run first so its applied before any tracer and other stuff going on.