Issue 6789 - Remove block-closing-brace-space-after stylelint rule

stylelint-config-eyeo/index.js

 /*
  * This file is part of Adblock Plus <https://adblockplus.org/>,
  * Copyright (C) 2006-present eyeo GmbH
  *
  * Adblock Plus is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 3 as
  * published by the Free Software Foundation.
  *
  * Adblock Plus is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
@@ skipping 14 matching lines @@
   rules: {
     // Opening braces go on their own line
     "block-opening-brace-newline-before": "always-multi-line",
     "block-opening-brace-newline-after": "always-multi-line",
     "block-closing-brace-newline-before": "always-multi-line",
     "block-closing-brace-newline-after": "always",
     "block-closing-brace-empty-line-before": "never",
 
     // Use a space between the last selector and the declaration block
     "block-opening-brace-space-before": "always-single-line",
-    "block-closing-brace-space-after": "always-single-line",
 
     // Use a space after a property name’s colon
     "declaration-colon-space-after": "always",
 
     // Selectors and declarations should be on their own line
     "selector-list-comma-newline-after": "always",
     "declaration-block-semicolon-newline-after": "always-multi-line",
 
     // Separate rules by an empty line
     "rule-empty-line-before": ["always", {
@@ skipping 28 matching lines @@
     // Font weight values should be specified in relative or numerical notation
     "font-weight-notation": ["numeric", {
       "ignore": ["relative"]
     }],
 
     // CSS rule declaration order should follow the WordPress CSS
     // Coding Standards
     "order/properties-order": require("./css-properties-order")
   }
 };