Require reflection for disabling cops

Is your feature request related to a problem? Please describe.

It's arguably "too easy" to just disable a cop. Like a free bribe oxymoron.

Describe the solution you'd like

For every Enabled: false:

1. Require a Reason: to make users reflect on their reluctance (and prompt imminent reconsideration)
2. Generate a Count: for each full directory tree run that shows magnitude of malpractice

• Low counts: Low hanging fruit to fix and get rid of cop altogether
• High counts: Indentifies greater pattern of blind spot in programming habits

1. Sort statements by count ascending

Describe alternatives you've considered

• Roll own (sort of did).
• (In addition), a wiki that specifically targets the (imagined) hurdles that maintain old habits, shows flawed premises of objections and how it's actually easier and better than feared. A learning journey, rather than a blunt "Bad" / "Good" example. And for the love of OOP, no "Car"/ "Wheel" examples!!

If One Is Truly to Succeed in Leading a Person to a Specific Place, One Must First and Foremost Take Care to Find Him Where He is and Begin There. – Søren Kierkegaard

Additional context

Verbose form:

Style/GlobalVars:
  Enabled: false
  Reason: Will cause too much boilerplate, everything must be shared/passed around
  Count: 64

Terse form (ie. any value that is not a single lowercase word will mean Enabled: false)

Style/GlobalVars:
  Enabled: (64) Will cause too much boilerplate, everything must be shared/passed around