Fix create_versions migration to support Ruby3

[joeytepp]

The create_versions migration created by doing bundle exec rails generate paper_trail:install is not compatible with Ruby3. This PR updates the migration so that it will be compatible

Check the following boxes:

• Wrote good commit messages.
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Added an entry to the Changelog if the new
  code introduces user-observable changes.
• The PR relates to only one subject with a clear title
  and description in grammatically correct, complete sentences.

[batter]

Does this remove compatibility with Ruby 2 in any capacity?

[joeytepp]

@batter No, keyword arguments were introduced in Ruby 2.0

[mathieujobin]

I am curious why the tests were not failing on ruby 3 before?

[joeytepp]

@mathieujobin they weren't failing because the migration still succeeds, however in the schema.rb file we end up with

    t.string "{:null=>false, :limit=>191}"

instead of

    t.string :item_type, null: false, limit: 191

This is due to the fact that Ruby 3 interprets the hash { null: false, limit: 191 } as a second argument instead of keyword arguments. So it needs to be explicitly passed as keyword arguments.

[jaredbeck]

Thanks for the contribution. Please add an entry to the changelog under Unreleased -> Fixed.

[joeytepp]

@jaredbeck updated the changelog 👍

[jaredbeck]

Thanks, Joey

[tinacious]

In existing projects, what do we need to do to get these changes applied retroactively? I've updated the gem to 12.3.0 but am still seeing the mangled schema.rb file after running migrations. bundle exec rails g paper_trail:install fails as there's already a version created, and --force doesn't do anything (this is expected as the table exists). I'm on Rails 6.1.0 and Ruby ruby 3.0.2. Any help would be appreciated, thanks! 🙏