DimensionRepository should not need a flush

[alexander-schranz]

Currently the DimensionRepository does need a flush before the Dimension can be loaded this should not be the case, the queries should also keep the new unitofwork entities into it.

When Implemented the Skips can be removed from the tests:

SuluContentBundle/TestCases/Dimension/DimensionRepositoryTestCaseTrait.php

Lines 63 to 65 in 3ef2765

	if ($skipSave) {
	$this->markTestSkipped('Currently not implemented to findOneBy without saving.');
	}

Possible Solution:

Create a collection of unit of work entities and use criteria to filter it.

[niklasnatter]

This is not longer relevant because the DimensionRepositorywas removed in #174

[alexander-schranz]

@nnatter I think we still have a similar problem with the new DimensionContent when I save a content in a process with en and de it will create 2. It will create 2 unlocalizedDimension which will then end in a unique constraint error when flusing them.

[niklasnatter]

You are right 😕 I saw that you already added #179 for that, so we can keep this closed