Content packaged with test framework in engine interferes with other content

The extension packaged with the test framework defines some initialize items that are also defined by the config module. If a test depends on config content it fails because the slightly different content is loaded from the test framework instead. This content is often just for local tests in the engine itself. Eventually we should refactor this whole setup but for now we can do a quick fix by renaming the initialize items and executing them after the ones in the config module so they don't have precedence.