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/namespacetransformer/NamespaceTransformer_test.go

@@ -80,15 +80,22 @@ metadata:
 
 	th.AssertActualEqualsExpected(rm, `
 apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: cm1
+  namespace: test
+---
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: cm2
+  namespace: test
+---
+apiVersion: v1
 kind: Namespace
 metadata:
   name: ns1
 ---
-apiVersion: apiextensions.k8s.io/v1beta1
-kind: CustomResourceDefinition
-metadata:
-  name: crd
----
 apiVersion: v1
 kind: ServiceAccount
 metadata:
@@ -116,17 +123,10 @@ subjects:
   name: another
   namespace: random
 ---
-apiVersion: v1
-kind: ConfigMap
+apiVersion: apiextensions.k8s.io/v1beta1
+kind: CustomResourceDefinition
 metadata:
-  name: cm1
-  namespace: test
----
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: cm2
-  namespace: test
+  name: crd
 `)
 }