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

pkg/target/configmaps_test.go

@@ -190,7 +190,7 @@ configMapGenerator:
   - from=base
 `)
 	th.WriteK("/app/overlay/o1", `
-bases:
+resources:
 - ../../base1
 configMapGenerator:
 - name: com1
@@ -199,7 +199,7 @@ configMapGenerator:
   - from=overlay
 `)
 	th.WriteK("/app/overlay/o2", `
-bases:
+resources:
 - ../../base2
 configMapGenerator:
 - name: com2
@@ -208,7 +208,7 @@ configMapGenerator:
   - from=overlay
 `)
 	th.WriteK("/app/overlay", `
-bases:
+resources:
 - o1
 - o2
 configMapGenerator: