Exclude jedis instrumentation from Indy-automigration

[JonasKunz]

Looks like #9654 uncovered some new indy test failures. Those suddenly appeared in #9565 after a rebase.

I think those exceptions come from the fact that some jedis instrumentations are applied even though they shouldn't, likely because the muzzle check is not active yet.

After some more looking I think the reason is actually that the Advice passes a JedisRequestContext from enter to exit. This type is then present on the stack of the instrumented method, causing it to fail because JedisRequestContext is not injected anymore.

Please add the test Indy label to this PR to verify it actually fixes the build.

[laurit]

There are some other tests where indy is disabled for the same reason. It could be fixed by returning Object instead and casting in the exit advice, but that isn't too nice. I think this could probably be worked around by changing bytebuddy.