Disable Style/MethodCallWithArgsParentheses cop for migrations

[obie]

Same rationale as disabling this cop for Gemfile (the source is a DSL and reads worse with parentheses)

[paracycle]

Hmm, I am not sure if a blanket exclusion for migration files is the best thing to do. We want to exclude only because things like create_table, etc read better as DSLs, but people are not limited to writing those in migration files, and we probably do want to lint all other method calls.

[rafaelfranca]

We decided to not make distinctions with DSLs. Everything should have parentheses. #100 (comment)

#106 (comment)

[rafaelfranca]

I wonder if we can see why migrations aren't considered macros that are allowed. I'm ok with this exception, but I'd like to maybe not add exceptions and maybe teach rubocop about those kind of macros.

[sambostock]

Using an example migration from the Rails docs:

# db/migrate/20240502100843_create_products.rb
class CreateProducts < ActiveRecord::Migration[8.0]
  def change
    create_table :products do |t|
      t.string :name
      t.text :description

      t.timestamps
    end
  end
end

I believe "macros" are loosely defined as methods called within a module/class body:

class Post < ApplicationRecord
  belongs_to :user # macro
end

User = Class.new(ApplicationRecord)
User.has_many(:posts) # not macro

By that definition, nothing in that migration is a "macro".