Look into setting test server class before starting mini accumulo

[keith-turner]

          I'd bet that there are some other tests, related to Scan Servers and/or External Compactions, that could use this new method instead of stopping the "normal" implementation and starting a different one for the test. It's probably worth a new ticket for this.

Originally posted by @dlmarion in #4643 (comment)

[keith-turner]

This issue is about determining if tests that call the following method

accumulo/minicluster/src/main/java/org/apache/accumulo/miniclusterImpl/MiniAccumuloClusterControl.java

Line 131 in f046289

public synchronized void start(ServerType server, Map<String,String> configOverrides, int limit,

could use the following pattern instead.

accumulo/test/src/main/java/org/apache/accumulo/test/functional/MergeFlakyFateIT.java

Lines 33 to 35 in f046289

	public void configureMiniCluster(MiniAccumuloConfigImpl cfg, Configuration hadoopCoreSite) {
	cfg.setServerClass(ServerType.MANAGER, FlakyFateManager.class);
	}

Probably depends on if the test uses the normal server class that was started before it starts a test one.

[dlmarion]

Probably depends on if the test uses the normal server class that was started before it starts a test one.

It probably only makes sense to use this new method when the test class only uses a single non-standard implementation. If the test class starts and stops different types of implementations, then this likely can't replace that functionality.

[cshannon]

@keith-turner - I think this can be closed after #4811, unless you had anymore tests you wanted to change. I looked and the other tests did not seem to be able to easily use this