test: Add a check for too long or badly reflowed docstrings

This ensures that docstring comments are wrapped to 80 chars. ffrank
seemed to be making this mistake far too often, and it's a silly thing
to look for manually. As it turns out, I've made it too, as have many
others. Now we have a test that checks for most cases. There are still a
few stray cases that aren't checked automatically, but this can be
improved upon if someone is motivated to do so.

Before anyone complains about the 80 character limit: this only checks
docstring comments, not source code length or inline source code
comments. There's no excuse for having docstrings that are badly
reflowed or over 80 chars, particularly if you have an automated test.

etcd/client/resources/resources.go

@@ -114,11 +114,11 @@ func SetResources(ctx context.Context, client interfaces.Client, hostname string
 	return err
 }
 
-// GetResources collects all of the resources which match a filter from etcd.
-// If the kindfilter or hostnameFilter is empty, then it assumes no filtering...
+// GetResources collects all of the resources which match a filter from etcd. If
+// the kindfilter or hostnameFilter is empty, then it assumes no filtering...
 // TODO: Expand this with a more powerful filter based on what we eventually
 // support in our collect DSL. Ideally a server side filter like WithFilter()
-// We could do this if the pattern was $NS/exported/$kind/$hostname/$uid = $data.
+// could do this if the pattern was $NS/exported/$kind/$hostname/$uid = $data.
 func GetResources(ctx context.Context, client interfaces.Client, hostnameFilter, kindFilter []string) ([]engine.Res, error) {
 	// key structure is $NS/exported/$hostname/resources/$uid = $data
 	path := fmt.Sprintf("%s/exported/", ns)