Since #490 made RuboCop 1.72+ a runtime requirement, `cop_enabled?` can now be used.

…er offenses for `Array#include?` that are optimized directly in Ruby.

Since `include?` on arrays are the only instances I ever run across this cop, I think it makes sense to add special handling for this.

On Ruby 3.4 this does no array allocations:
```
require "memory_profiler"

class Foo
  def bar
    Bar.new
  end
end

class Bar
  def baz
  end
end

foo = Foo.new
report = MemoryProfiler.report do
  [1,2].include?(foo.bar.baz)
end.pretty_print
```

Also, this code is simply slower on Ruby 3.4:

```rb
require "benchmark/ips"

local = [301, 302]
val = 301
Benchmark.ips do |x|
  x.report('local') do
    local.include?(val)
  end

  x.report('literal') do
    [301, 302].include?(val)
  end
  x.compare!
end
```

```
$ ruby test.rb
ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
Warming up --------------------------------------
               local     1.822M i/100ms
             literal     2.296M i/100ms
Calculating -------------------------------------
               local     18.235M (± 1.6%) i/s   (54.84 ns/i) -     92.906M in   5.096277s
             literal     22.807M (± 1.5%) i/s   (43.85 ns/i) -    114.789M in   5.034289s

Comparison:
             literal: 22806932.0 i/s
               local: 18235340.7 i/s - 1.25x  slower
```

Follow up rubocop/rubocop#13908.

Change `Performance/CollectionLiteralInLoop` to not register offenses for `Array#include?` that are optimized directly in Ruby.

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-performance` repository has essentially the same structure as the `rubocop` repository,
so it should work as is.

…ent`

This PR fixes false positives for `Performance/StringIdentifierArgument`
when using interpolated string argument.
Converting a string with interpolation into a symbol degrades performance.

Fixes #492.

…_string_identifier_argument

[Fix #492] Fix false positives for `Performance/StringIdentifierArgument`

…h a `numblock`

Fix `Performance/FixedSize` false positive when `count` is called with a `numblock`

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

Support `it` block parameter in `Performance` cops