CI may unintentionally use fallback akka loader

We have a fallback akka loader for developer convenience in the IDE, that is on the classpath of most modules. Depending on the order of jars on the classpath it can happen that the fallback loader appears first, which we dont want because it slows down the build and creates noisy logs.

We can add a simple prioritization scheme to the rpc system loading to remedy that.