[FIX #4723] RaiseArgs shouldn't autocorrect 3-args form

[smakagon]

Fixes the auto-correction issue for raise with 3 arguments:

Without this fix, the following code:

begin
  1 / 0
rescue => e
  raise StandardError, 'hi', e.backtrace
end

would be auto-corrected to the broken one:

begin
  1 / 0
rescue => e
  raise StandardError.new('hi', e.backtrace) # wrong number of arguments (given 2, expected 0..1) (ArgumentError)
end

With this fix, any raise with more than 2 arguments will not be autocorrected.

---

Before submitting the PR make sure the following are checked:

• Wrote good commit messages.
• Commit message starts with [Fix #issue-number] (if the related issue exists).
• Used the same coding conventions as the rest of the project.
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
• All tests(rake spec) are passing.
• The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
• The PR relates to only one subject with a clear title
  and description in grammatically correct, complete sentences.
• Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

[Drenmi]

I like the unification of the arguments to these sister methods. 👍

[Drenmi]

I think the examples in the class documentation need to be updated. Other than that, all the changes look good! 🚀

[smakagon]

@Drenmi Thanks for the review. How would you like to change documentation? Do you want me to add a note for auto-correction behavior?

[Drenmi]

@smakagon: Hm. I thought this invalidated some example in the documentation, but now thinking I might've been wrong. 🙂