[rc vehicle fleet rips mgk] Include settings to quiet unagreed-upon RuboCops in our applications.

- rc: find . -type f -not -path '*vendor*' -not -path '*test*'  -name '*.rb' |xargs ridecharge-rubocop -R -f o
  - 1507 files inspected, 1381 offences detected (almost all tab offenses)
  - 1369  Tab
  - 7     ParameterLists
  - 4     BlockNesting
  - 1     LineLength
- rips: ridecharge-rubocop -R -f o
  - 618 files inspected, 39 offences detected (almost all tab offenses)
  - 21  Tab
  - 12  Syntax
  - 3   BlockNesting
  - 1   ParameterLists
  - 1   EnsureReturn
  - 1   CyclomaticComplexity
- fleet-magic: ridecharge-rubocop -R
  - 552 files inspected, no offences detected
- vehicle: ridecharge-rubocop -R
  - 194 files inspected, no offences detected


I created these -todos.yml files by running 
`ridecharge-rubocop -R --auto-gen-config`
in each repo, then adding the generated config here. They are in most-lenient first order for a reason; rubocop overwrites earlier settings with later settings. 
The goal is to get to where we have a consistent standard. 

I then `rake install`ed the gem again, and reran `ridecharge-rubocop -R` in each repo to see if any non-Tab cops detected offenses.

Those which did were differences between the required lengths of class files and methods. The maximum required for those cops are from RC. Those settings are present as overrides in `standard-todo.yml`, I wanted to bring the greatest differences between applications to light.

The expected workflow would be this:
A) Get `ridecharge-rubocop` integrated into each application.
B) Get to the point where the `config/standard-todos.yml` reflects our actual desire for those 4-5 Cops. Then apply those settings to their own files, and remove them from `config/standard-todos.yml`. Then add all the unique settings in reverse order of the other `-todos.yml` files. That can then be the standard we work off of.