add outer padding to rule padded-blocks and cover existing jscs functionality

Update: please refer to this pull request for the current status of this issue:

https://github.com/eslint/eslint/pull/8099

1st proposal: updating padded-blocks

{
  inner: "always" | "never" | "before" | "after"
  outer: "always" | "never" | "before" | "after"
  prefer: "inner" | "outer"
  outerExceptions: "inCallExpressions" | "inNewExpressions" | "inArrayExpressions" | "inProperties" | "singleLine"
  innerExceptions: "blocks" | "classes" | "switches"
}

The above doesn’t yet include additional options for backwards compatibility.

related issues:

• https://github.com/eslint/eslint/issues/3092
• https://github.com/eslint/eslint/issues/5982
• https://github.com/eslint/eslint/issues/5949

related / converging rules:

• http://jscs.info/rule/requirePaddingNewLinesAfterBlocks.html
• http://eslint.org/docs/rules/padded-blocks
• I think jscs has another rule for padding before blocks?

2nd proposal

no modifications to padded-blocks. new rule that has exceptions to allow padded-blocks to work, if there is a conflict an error is thrown (is this even a thing?)

"padding-around-blocks": true | "before" | "after", {
  "exceptions": "inCallExpressions" | "inNewExpressions" | 
                "inArrayExpressions" | "inProperties" | "singleLine" | 
                "afterOpeningBlock" | "beforeEndingBlock"
}

"afterOpeningBlock" and "beforeEndingBlock" specify whether the rule should apply to a block placed at the beginning or end of the inside of another block. If they are both specified, then padded-blocks should work as expected. If they are not specified, then the new rule could potentially result in an error depending how padded-blocks is configured.

[alberto]

Also thanks to everyone who contributed in the discussion or with a PR and helped us flesh this out! special hat tip to @quinn @TheSavior @LinusU @ekmartin

We know it has been painfully slow, and we apologize for that

[kaicataldo]

@alberto Sure thing - I’ll try to get to it tonight. @quinn Thanks for sticking with us and for all the thought you’ve put into this - your help has been invaluable!