[The official Ruby Style guide](https://rubystyle.guide/#no-rescue-modifiers) recommends
avoiding the use of `rescue` in its modifier form. It does somewhat beg the question of
why include a modifier form in the first place, but that's just by the by.

Quoting from Rubocop documentation, this rule:

> Checks for uses of `rescue` in its modifier form is added for following reasons:
>
> - The syntax of modifier form `rescue` can be misleading because it might lead us to
>   believe that `rescue` handles the given exception but it actually rescue all exceptions
>   to return the given rescue block. In this case, value returned by handle_error or
>   SomeException.
>
> - Modifier form`‘rescue` would rescue all the exceptions. It would silently skip all
>   exception or errors and handle the error.  Example: If `NoMethodError` is raised,
>   modifier form rescue would handle the exception.

Initial fix applied automatically with `bundle exec rubocop --autocorrect-all --only
Style/RescueModifier`; I then manually ran a few more autocorrect commands to fix up some
of the indentation and layout errors produced by the initial autocorrection.

- https://rubystyle.guide/#no-rescue-modifiers
- https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Style/RescueModifier
- https://docs.rubocop.org/rubocop/cops_style.html#stylerescuemodifier

To match what we believe the original intent was, rather than to
preverse existing (and likely broken) original functionality.

See the commit that introduced this behavior for more context:
d04d412