Prohibit Futures.addCallback(Future, Callback) (i. e. using directExecutor() implicitly) using forbidden-apis

[This method is deprecated and removed from later versions of Guava for good reasons.](https://guava.dev/releases/22.0/api/docs/com/google/common/util/concurrent/Futures.html#addCallback-com.google.common.util.concurrent.ListenableFuture-com.google.common.util.concurrent.FutureCallback-) Using this method mindlessly causes problems like #8445.

While Druid is stuck with older Guava, it should prohibit the problematic method proactively using forbidden-apis, forcing specifying an executor explicitly, and actually thinking about which executor should be used.

There are currently 19 usages of this method in Druid production code.

Start by locating Druid's forbidden-apis configuration and searching production code for the 19 Futures.addCallback(Future, Callback) usages. Update the prohibition and review each usage to specify an appropriate executor explicitly; done means the problematic overload is rejected and the build passes with all usages migrated.

Written by the indexing model from the issue text.