Fix Style/MethodCallWithArgsParentheses for endless method definitions

[dvandersluis]

When an endless method definition calls another method with arguments, parentheses are required or it will be a syntax error. Therefore, parentheses are required even for the omit_parentheses style. If there are no arguments, the method call will continue to be matched to the enforced style as before.

---

Before submitting the PR make sure the following are checked:

• The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• Wrote good commit messages.
• Commit message starts with [Fix #issue-number] (if the related issue exists).
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
• Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

[bbatsov]

When an endless method definition calls another method with arguments, parentheses are required or it will be a syntax error. Therefore, parentheses are required even for the omit_parentheses style. If there are no arguments, the method call will continue to be matched to the enforced style as before.

I dislike those methods even more now. 😆 You should put this and the other required parens (for defs with no params) into the rationale of the style guide entry.