Modify tests to present expected data in unsorted order.

Modify all `build` tests to use the raw,
non-sorted output of build.  This makes every test
provide coverage for how kustomize re-orders (or
doesn't reorder) resources during processing.

Going forward, the ordering of resources in
_expected_ output should match the depth-first
ordering specified in the `resources:` field used
in the test's kustomization file.

The only exception to this rule would be tests
that actually confirmed some other output
ordering, e.g. the test of the
`LegacyOrderTransformer` plugin.

Fixes #756
Related #821

plugin/builtin/inventorytransformer/InventoryTransformer_test.go

@@ -99,7 +99,7 @@ name: pruneCM
 namespace: default
 `, content)
 
-	th.AssertActualEqualsExpected(rm, inv+"---"+content)
+	th.AssertActualEqualsExpected(rm, content+"---"+inv)
 }
 
 func TestInventoryTransformerDefaultPolicy(t *testing.T) {
@@ -120,5 +120,5 @@ name: pruneCM
 namespace: default
 `, content)
 
-	th.AssertActualEqualsExpected(rm, inv+"---"+content)
+	th.AssertActualEqualsExpected(rm, content+"---"+inv)
 }