Explicit route test class

shows the class that the test must extend in order to have the assert_routing method available
If Rails is not defined, check ENV["RAILS_ENV"] and ENV["RACK_ENV"].

This fixes a regression introduced by 6cc03675d30b58e28f585720dad14e947a57ff5b.

ActiveRecord, if used without Rails, always checks the "default_env" environment. This would be OK, except that Sinatra also supports environments,
and it runs with {RACK|RAILS}_ENV=production. This patch adds a fallback to RAILS_ENV and RACK_ENV (and ultimately default_env) if Rails.env doesn't exist.
[ci skip] Add missing blank line to AR validation.
[ci skip] No need to indent here (AC overview).
[ci skip] Add highlight to code (form helper guide).
Make `String#remove` and `String#remove!` accept multiple arguments
Do not package the guides output

Fixes #17455
Don't require calculations to be aliased to a column

Arel has changed so that `.sum` no longer aliases `SUM(the_column)` to
`sum_id`. This means the type returned by the adapter will be at the key
`"SUM(the_column)"`. Longer term, we should eventually be able to retain
type information from the AR::Base subclasses used in joined queries
Rename `default_attributes` to `_default_attributes`

It is internal use only. This is to avoid conflicting with users' method
names. Fixes #17458
Add masked authenticity token section, details on finder options, misc typos [ci skip]
Merge pull request #17460 from hbriggs/master

Masked authenticity token section, finder options details, misc typos [ci skip]
Treat strings greater than int max value as out of range

Sufficiently large integers cause `find` and `find_by` to raise
`StatementInvalid` instead of `RecordNotFound` or just returning `nil`.
Given that we can't cast to `nil` for `Integer` like we would with junk
data for other types, we raise a `RangeError` instead, and rescue in
places where it would be highly unexpected to get an exception from
casting.

Fixes #17380
Merge pull request #17459 from sgrif/sg-find-by-large-numbers

Treat strings greater than int max value as out of range
Honor public/private in ActionView::Helpers::Tags::Base#value

* use public_send instead of send to avoid calling private
  methods in form helpers
Use public_send for form tags
Improve test of private properties of objects in form tags
Merge branch 'tags-public-send'

Fixes #14180
Fixes #17461
Tiny documentation improvements [ci skip]
Use the correct values for int max and min

We had accidentally gone one power of two too far. In addition, we need
to handle minimum values as well as the maximum.
- Changed redundant user of `deliver` to `deliver_now`
- Wrapped text in setting defaults section. Also added break, to a sentence.
[ci skip]