Use `SchemaStatements#initialize_schema_migrations_table` instead of `ActiveRecord::SchemaMigration.create_table`.
Add positional information to eval call so that this information will
be used in printing correct location where the exception occurred.
Closes #12885

- Without this the location of exception is always the line on which
  'eval' is called
- But if the exception occurs in a gem outside of Rails, then that
  location is not printed in stacktrace
Fix ActiveRecord::Relation#unscope

I'm pretty confused about the addition of this method. The documentation
says that it was intended to allow the removal of values from the
default scope (in contrast to #except). However it behaves exactly the
same as except: https://gist.github.com/jonleighton/7537008 (other than
having a slightly enhanced syntax).

The removal of the default scope is allowed by
94924dc32baf78f13e289172534c2e71c9c8cade, which was not a change we
could make until 4.1 due to the need to deprecate things. However after
that change #unscope still gives us nothing that #except doesn't already
give us.

However there *is* a desire to be able to unscope stuff in a way that
persists across merges, which would allow associations to be defined
which unscope stuff from the default scope of the associated model. E.g.

  has_many :comments, -> { unscope where: :trashed }

So that's what this change implements. I've also corrected the
documentation. I removed the guide references to #except as I think
unscope really supercedes #except now.

While we're here, there's also a potential desire to be able to write
this:

  has_many :comments, -> { unscoped }

However, it doesn't make sense and would not be straightforward to
implement. While with #unscope we're specifying exactly what we want to
be removed from the relation, with "unscoped" we're just saying that we
want it to not have some things which were added earlier on by the
default scope. However in the case of an association, we surely don't
want *all* conditions to be removed, otherwise the above would just
become "SELECT * FROM comments" with no foreign key constraint.

To make the above work, we'd have to somehow tag the relation values
which get added when evaluating the default scope in order to
differentiate them from other relation values. Which is way too much
complexity and therefore not worth it when most use cases can be
satisfied with unscope.

Closes #10643, #11061.
Expand double-negative in String#blank? regex
Merge pull request #12976 from tmm1/faster-blank

Faster String#blank?
replace U+00A0 with whitespace
Merge pull request #12986 from budnik/fix-unicode-nbsp

replace U+00A0 with whitespace, Fixes #12985
Merge pull request #12970 from prathamesh-sonpatki/issue12885

Add positional information to eval call so that this information will be used in printing correct location where the exception occurred.

Closes #12885.
replace custom Time stubbing with `travel` and `travel_to`.
Fix for routes task

This commit fixes formatting issue for `rake routes` task, when a section is shorter than a header.
doc `travel` and `travel_to` stubs are removed in teardown. [ci skip]
Merge pull request #12975 from sbagdat/fix-for-rake-routes

Fix for routes task
unify punctuation in Action Pack changelog. [ci skip]
Merge pull request #12962 from kamipo/call_initialize_schema_migrations_table_from_migration

Use `SchemaStatements#initialize_schema_migrations_table` instead of `ActiveRecord::SchemaMigration.create_table`.
Remove unused param `options` to `TransitionTable#as_json`