Refactor use of ServerConfigurationFactory

[milleruntime]

Divided this PR into 2 commits:
1 - Deprecates the init method in MemoryManager that took ServerConfigurationFactory as a parameter. Replace it with a method that takes ServerContext. Updated Test to mock ServerContext.
2 - Inline some of the methods of ServerConfigurationFactory into ServerContext to reduce references to it. Removed sychronization on the methods now they are a part of ServerContext because i don't think its needed since each server should only have one instance. This is just a first step into eliminating internal use of ServerConfigurationFactory.

Update: Broke out changes to MemoryManager in a separate branch.

[ctubbsii]

I like the overall changes. I think this might prompt follow-up work, though.

[ctubbsii]

I don't think there's any reason to load this singleton lazily.

Suggested change

	if (defaultConfig == null) {
	defaultConfig = DefaultConfiguration.getInstance();
	}
	return defaultConfig;
	return DefaultConfiguration.getInstance();

[milleruntime]

Perhaps this method is poorly named because it just returns a new object:

public static DefaultConfiguration getInstance() {
    return new DefaultConfiguration();
  }

I think it is worth storing a local copy to prevent creating too many identical objects.

[ctubbsii]

The class is documented as a singleton... but that appears to have stopped being the case as of 37f900b ; it should be a singleton. It doesn't need to do all the synchronization that the commit cleaned up, but it should still save and reuse the single instance.

[milleruntime]

Yeah and since it anything loading the class will use it, I think it could just be created once during class load as a static variable.