Relocate misplaced files #5867
Description
To ensure we can seal jars during our build, we organize files in separate jars into mutually exclusive packages/resource directories. To ensure this mutual exclusivity, we have a convention of having package/directory names based on the Maven module that builds that jar. (for example, the core module that builds accumulo-core.jar uses a base package of org.apache.accumulo.core).
However, we break this convention in several places. Some of these are okay, like how the minicluster module has packages org.apache.accumulo.minicluster and also org.apache.accumulo.miniclusterImpl. This is okay because the package name is still clearly associated with that same Maven module, and there are some reasons we might want to have the implementation classes off to the side, rather than underneath, the base package (for example, to document the public API definition more simply).
In other cases, we don't need to break the convention, and we should generally follow the convention whenever possible. In PR #5866, a CI check was added to prevent new convention breakages, and to document the current exceptions.
This task is to work through the current exceptions, and relocate them, so that we do not need as many exceptions documented in that CI check.