Removed the brace-style ESLint exclusion

[dbemiller]

Type of change

Code style update (formatting, local variables)

Description of change

Fixing one of the linter exceptions for #1206.

Everything was done with lint --fix except for the following three spots, which I fixed manually:

dbemiller-mac:Prebid.js dbemiller$ ./node_modules/eslint/bin/eslint.js src modules/ --fix

/Users/dbemiller/code/Prebid.js/src/adloader.js
  45:3  error  Closing curly brace does not appear on the same line as the subsequent block  brace-style

/Users/dbemiller/code/Prebid.js/src/bidmanager.js
  230:3  error  Closing curly brace does not appear on the same line as the subsequent block  brace-style

/Users/dbemiller/code/Prebid.js/modules/rhythmoneBidAdapter.js
  124:63  error  Closing curly brace does not appear on the same line as the subsequent block  brace-style

[mkendall07]

This is harder to read than before. It doesn't look like standardjs implements a max-len but I think we should consider it. I guess it doesn't do that because it can't --fix that automatically?

[dbemiller]

I'm not sure why standardjs doesn't define one... but I agree, this is harder to read this way. For now I'll split it up manually.

We should consider max-len in the future. In my experience that rule ends up being ~80% good, 20% bad. It prevents code like this, which is great, but it can be a negative if you want to write long error messages or string constants.

I'd still be in favor of it though. You can always disable the linting rules for your line, if you have a really good case for it.