remove 'automatically generated' strings from repo (#1412)

Maintainers use an import organizer called 'gci' that ignores files with
the string 'automatically generated' when called with its
--skip-generated flag.

This commit is the result of the following command:

```
rg ' automatically generated' -l | xargs -n1 sed -i 's/ automatically generated//g'
```

None of the changed files are _actually_ generated files. We do not want
gci to think they are.

Signed-off-by: Joe Lanford <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: b12dea86e3642f7644be766bfdd0ca3b79ffdc30

Author: joelanford

staging/operator-registry/README.md

@@ -17,7 +17,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/bundles/etcd.0.9.0/manifests/etcdoperator.v0.9.0.yaml

@@ -17,7 +17,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/bundles/etcd.0.9.2/manifests/etcdoperator.v0.9.2.clusterserviceversion.yaml

@@ -5724,7 +5724,7 @@ data:
 
           ### Reading and writing to etcd
 
-          Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+          Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
           [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 
@@ -5901,7 +5901,7 @@ data:
 
           ### Reading and writing to etcd
 
-          Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+          Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
           [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 
@@ -6196,7 +6196,7 @@ data:
 
           ### Reading and writing to etcd
 
-          Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+          Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
           [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/configmap.example.yaml

@@ -16,7 +16,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/manifests/etcd/0.6.1/etcdoperator.clusterserviceversion.yaml

@@ -17,7 +17,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/manifests/etcd/0.9.2/etcdoperator.v0.9.0.yaml

@@ -24,7 +24,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/manifests/etcd/0.9.2/etcdoperator.v0.9.2.clusterserviceversion.yaml

@@ -17,7 +17,7 @@ spec:
 
     ### Reading and writing to etcd
 
-    Communicate with etcd though its command line utility `etcdctl` or with the API using the automatically generated Kubernetes Service.
+    Communicate with etcd though its command line utility `etcdctl` or with the API using the Kubernetes Service.
 
     [Read the complete guide to using the etcd Open Cloud Service](https://coreos.com/tectonic/docs/latest/alm/etcd-ocs.html)
 

staging/operator-registry/pkg/api/conversion_test.go

@@ -152,7 +152,7 @@ spec:
     \n\n### Reading and writing to etcd\n\nCommunicate with etcd though its command\
     \ line utility `etcdctl` via port forwarding:\n\n    $ kubectl --namespace default\
     \ port-forward service/example-client 2379:2379\n    $ etcdctl --endpoints http://127.0.0.1:2379\
-    \ get /\n\nOr directly to the API using the automatically generated Kubernetes\
+    \ get /\n\nOr directly to the API using the Kubernetes\
     \ Service:\n\n    $ etcdctl --endpoints http://example-client.default.svc:2379\
     \ get /\n\nBe sure to secure your etcd cluster (see Common Configurations) before\
     \ exposing it outside of the namespace or cluster.\n\n\n### Supported Features\n\