Most likely this is caused by a bug in the MovingAverageModule itself where the bindings are not being properly lazy.
That said, the coordinator/overlord do not participate in queries and therefore do not need the extension on the class path. You can work around the bug in the module by not including the extension on the classpath of the coordinator/overlord. But you should likely also raise a bug against the extension itself showing that it fails when included on non-querying nodes. The bindings should be lazy such that they only actually load things if the query machinery is loaded.