Rule request: Enforce whether or not parentheses should be wrapped around closures

Currently closures can be written one of two ways:
myCollection.filter{ $0 == 1 }
or
myCollection.filter({ $0 == 1 })

These two different ways are identical and will run exactly the same way. Further more, this also extends to closures with multiple lines:

let newCollection = myCollection.map{ 
  2*$0 + 5
}

or

let newCollection = myCollection.map({ 
  2*$0 + 5
})

For this, I propose a new rule which allows the presence of parentheses to be required, or disallowed depending on the configuration. Furthermore, I think the rule should allow you to differentiate between inline closures and multi line closures. For instance, with a particular configuration this would be allowed:

myCollection.filter({ $0 == 1 })
let newCollection = myCollection.map {
    2*$0 + 5
}

The issue names no implementation files, tests, or entry points. Start by reviewing SwiftLint's existing rule and configuration patterns, then determine how inline and multiline closures should be distinguished and how both required and disallowed parentheses should be validated; done means the rule and its configuration behavior are covered by tests.