…nClassName

https://github.blog/changelog/2023-12-14-new-markdown-extension-alerts-provide-distinctive-styling-for-significant-content/

…hod-calls-on-local-variables

ReflectionClassName: accept method calls on local variables

Make `Lint/UselessAccessModifier` aware of `ActiveSupport::Concern`

Follow up rubocop/rubocop#13908.

This fixes both false positives and negatives:
* Since Rails 7.2, the first argument yielded is the transaction itself
* Don't register an offense when breaking out of a numblock loop

Followup to #1450

…ocks

This should also take care of #1413, once `itblock` is introduces

Make `Rails/SaveBang` aware of numblocks

…with numblock

There's also up_only and similar, but they don't yield any arguments

Make `Rails/TransactionExitStatement` aware of numblocks

Disable `Rails/Delegate` for controllers

Fix a false positive for `Rails/CreateTableWithTimestamps` with numblocks

…le-numblock

Fix a false positive for `Rails/ReversibleMigration` in `drop_table` with numblock

…a lambda/proc with numblock

…k with `uniq`

Fix a false positive for `Rails/RelativeDateConstant` when assigning a lambda/proc with numblock

Fix a false positive for `Rails/UniqBeforePluck` when using a numblock with `uniq`

Follow-up to rubocop/rubocop#13929

This commit suppresses the following RuboCop's offenses:

```console
$ bundle exec rubocop
(snip)

lib/rubocop/cop/mixin/active_record_helper.rb:106:40:
C: [Correctable] InternalAffairs/NodeTypeGroup: Use :call instead of individually listing group types.
        send_node = node.each_ancestor(:send, :csend).first
                                       ^^^^^^^^^^^^^
lib/rubocop/cop/rails/pluck.rb:63:40:
C: [Correctable] InternalAffairs/NodeTypeGroup: Use :any_block instead of individually listing group types.
          return if node.each_ancestor(:block, :numblock).any?
                                       ^^^^^^^^^^^^^^^^^

301 files inspected, 2 offenses detected, 2 offenses autocorrectable
```

Follow-up to https://github.com/rubocop/rubocop/blob/master/.github/workflows/github_release.yml.

This action will be triggered when a new tag is pushed and will
auto-fill the release notes using the relevant file.

The `rubocop-rails` repository has essentially the same structure as the `rubocop` repository,
so it should work as is.