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/prefixsuffixtransformer/PrefixSuffixTransformer_test.go

@@ -48,6 +48,14 @@ metadata:
 `)
 
 	th.AssertActualEqualsExpected(rm, `
+apiVersion: v1
+kind: Service
+metadata:
+  name: baked-apple-pie
+spec:
+  ports:
+  - port: 7002
+---
 apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:
@@ -57,13 +65,5 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: baked-cm-pie
----
-apiVersion: v1
-kind: Service
-metadata:
-  name: baked-apple-pie
-spec:
-  ports:
-  - port: 7002
 `)
 }