This way it's just checking for a block body instead of caring about the specific type

Rubocop already defined its own `blank?` method (🙁),
so ruby always warns when it is loaded again.

There's no real point in using the extension though, so just not using it seems ideal.

Fix #1465

This change avoids the printing of warnings about some methods
(`included`, `on_class`, and `on_send`) of the
`RuboCop::Cop::EnforceSuperclass` module being redefined. These warnings
are printed because, in addition to the definition of that module here
in `rubocop-rails`, that module is first [also defined in `rubocop`][1].
(The module has been extracted to `rubocop-rails`, but is also left in
`rubocop`, for backwards compatibility.)

[1]: https://github.com/rubocop/rubocop/blob/v1.73.2/lib/rubocop/cop/mixin/enforce_superclass.rb

This change avoids the warnings by first undefining the
`RuboCop::Cop::EnforceSuperclass` module (the one from `rubocop`) before
then redefining that module here in `rubocop-rails`.

…ned-methods

Avoid warnings about redefined methods in EnforceSuperclass module

Don't load the active_support `blank` core extension

This commit suppresses the following RuboCop's offense:

```console
$ bundle exec rubocop
(snip)

lib/rubocop/cop/rails/eager_evaluation_log_message.rb:48:23:
C: [Correctable] Style/RedundantFormat: Use MSG directly instead of format.
            message = format(MSG)
                      ^^^^^^^^^^^

301 files inspected, 1 offense detected, 1 offense autocorrectable
```

Future-proof `Rails/Output` for `itblock`

This PR supports `it` block parameter in `Rails` cops.

Closes #1413

Support `it` block parameter in `Rails` cops

[Fix #1353] Fix incorrect escaping of asterisk in docs and comments