Fix an incorrect autocorrect for Lint/AmbiguousBlockAssociation

[koic]

This PR fixes the following incorrect autocorrect for Lint/AmbiguousBlockAssociation with Style/MethodCallWithArgsParentheses.

expect { foo }.not_to change { bar }

Before

$ bundle exec rubocop --only Lint/AmbiguousBlockAssociation,Style/MethodCallWithArgsParentheses -a
Inspecting 1 file
F

Offenses:

example.rb:1:1: W: [Corrected] Lint/AmbiguousBlockAssociation: Parenthesize the param change { bar } to make sure that the block will be associated with the change method call.
expect { foo }.not_to change { bar }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
example.rb:1:1: C: [Corrected] Style/MethodCallWithArgsParentheses: Use parentheses for method calls with arguments.
expect { foo }.not_to change { bar }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
example.rb:1:38: F: Lint/Syntax: unexpected token tRPAREN
(Using Ruby 3.2 parser; configure using TargetRubyVersion parameter, under AllCops)
expect { foo }.not_to(change { bar }))
                                     ^

1 file inspected, 3 offenses detected, 2 offenses corrected

Syntax error with redundant closing parentheses.

$ git diff .
diff --git a/x/example.rb b/x/example.rb
index 142ff55..6de7188 100644
--- a/x/example.rb
+++ b/x/example.rb
@@ -1 +1 @@
-expect { foo }.not_to change { bar }
+expect { foo }.not_to(change { bar }))

After

Valid syntax.

$ git diff .
diff --git a/x/example.rb b/x/example.rb
index 142ff55..7808ed5 100644
--- a/x/example.rb
+++ b/x/example.rb
@@ -1 +1 @@
-expect { foo }.not_to change { bar }
+expect { foo }.not_to(change { bar })

---

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.