…ther optionsWhen I've added new `:size` option inrails#35071, I've found that invalid`:limit` and `:precision` raises `ActiveRecordError` unlike otherinvalid options.I think that is hard to distinguish argument errors and statementinvalid errors since the `StatementInvalid` is a subclass of the`ActiveRecordError`.https://github.com/rails/rails/blob/c9e4c848eeeb8999b778fa1ae52185ca5537fffe/activerecord/lib/active_record/errors.rb#L103```rubybegin  # execute any migrationrescue ActiveRecord::StatementInvalid  # statement invalidrescue ActiveRecord::ActiveRecordError, ArgumentError  # `ActiveRecordError` except `StatementInvalid` is maybe an argument errorend```I'd say this is the inconsistency worth fixing.Before:```rubyadd_column :items, :attr1, :binary,   size: 10      # => ArgumentErroradd_column :items, :attr2, :decimal,  scale: 10     # => ArgumentErroradd_column :items, :attr3, :integer,  limit: 10     # => ActiveRecordErroradd_column :items, :attr4, :datetime, precision: 10 # => ActiveRecordError```After:```rubyadd_column :items, :attr1, :binary,   size: 10      # => ArgumentErroradd_column :items, :attr2, :decimal,  scale: 10     # => ArgumentErroradd_column :items, :attr3, :integer,  limit: 10     # => ArgumentErroradd_column :items, :attr4, :datetime, precision: 10 # => ArgumentError```

MySQL: Support `:size` option to change text and blob sizerails/rails#35071