Fix an incorrect autocorrect for Rails/SelectMap when select has no receiver and method chains are used

[masato-bkn]

This PR fixes an incorrect autocorrect for Rails/SelectMap when select has no receiver and method chains are used between select and map.

For example: select(:column_name).where(conditions).map(&:column_name)

Expected Behavior

where(conditions).pluck(:column_name)

Actual Behavior

.where(conditions)pluck(:column_name)

Steps to reproduce the problem

Run bundle ex rubocop -A --only Rails/SelectMap on the code below:

select(:column_name).where(conditions).map(&:column_name)

RuboCop version

1.67.0 (using Parser 3.3.5.0, rubocop-ast 1.32.3, analyzing as Ruby 3.2, running on ruby 3.2.0) [x86_64-darwin21]
  - rubocop-rails 2.27.0

---

Before submitting the PR make sure the following are checked:

• The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• Wrote good commit messages.
• Commit message starts with [Fix #issue-number] (if the related issue exists).
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
• Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
• If this is a new cop, consider making a corresponding update to the Rails Style Guide.

[masato-bkn]

When I added "model" to the test name in L59, Layout/LineLength pointed it out, so I removed it from this test name as well to keep the format consistent.

spec/rubocop/cop/rails/select_map_spec.rb:59:121: C: Layout/LineLength: Line is too long. [124/120]
  it 'registers an offense when using `select(:column_name).where(conditions).map(&:column_name)` without receiver model' do
                                                                                                                        ^^^^

[koic]

I think keeping git blame intact is more valuable, but it’s unlikely that anything significant will happen here.

[koic]

Thanks!