Blocks: Remove require-jsdoc eslint rule (#251)

Adding valid jsdoc comments to components (and each method in each component) is more noise than benefit. These are usually overly-generic and the components are just as understandable without them. We can trust a developer's best judgement for whether a function needs documentation, and the `valid-jsdoc` rule will still kick in to check the formatting.

public_html/wp-content/mu-plugins/blocks/.eslintrc.js

@@ -105,23 +105,6 @@ module.exports = {
 			ignoreStateless: true
 		} ],
 
-		/*
-		 * A short description often makes a function easier to understand, and also provides a nice visual
-		 * delineation between functions.
-		 *
-		 * Given that closures should be short and contextually relevant, requiring documentation for them would
-		 * likely hurt readability more than it would help clarity.
-		 */
-		'require-jsdoc': [ 'error', {
-			'require': {
-				'FunctionDeclaration'     : true,
-				'MethodDefinition'        : true,
-				'ClassDeclaration'        : true,
-				'ArrowFunctionExpression' : false,
-				'FunctionExpression'      : true
-			}
-		} ],
-
 		/*
 		 * Sort imports alphabetically, at least inside multiple-member imports. Ignores declaration sorting since
 		 * this interfers with the External/WordPress/Internal groupings. For example, it will flag the following