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/replicacounttransformer/ReplicaCountTransformer_test.go

@@ -109,16 +109,16 @@ spec:
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: myapp
+  name: otherapp
 spec:
-  replicas: 23
+  replicas: 5
 ---
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: otherapp
+  name: myapp
 spec:
-  replicas: 5
+  replicas: 23
 ---
 apiVersion: apps/v1
 kind: StatefulSet