Merge pull request #14000 from Fortisque/kevin/stream_error_management

streaming should change status of response when exception is caught
time helpers honor the application time zone when passed a date

Rails applications are expected to be always aware of the application
time zone.

To be consistent with that contract, we have to assume that a bare
date passed to time helpers is a date in the application time zone,
not in the system time zone. The system time zone is irrelevant, we
should totally ignore it.

For example,

    travel_to user.birth_date + 40.years

should make that user be 40th years old regardless of the system
time zone. Without this patch that may not be true.
adds a missing travel back
travel_to travels back and re-raises if the block raises
Updated doc for default scope [ci skip]
Tell default_scope are prepended [ci skip]
Fix parameter naming in RemoteIp middleware constructor method

Was custom_proxies in inline docs, but should be and defined in
constructor as custom_proxies
Aesthetic [ci skip]
Doc: assets:precompile:all was removed on 4 [skip ci]
Added Object#present_in to simplify value whitelisting
Merge pull request #14096 from arthurnn/precompile_all

Upgrade Doc: assets:precompile:all was removed on 4
Use assert_nil instead as its clearer about what the return is expected to be
Minor grammar/punctuation fixes [ci skip]
Move changelog entry to the top, fix examples indent [ci skip]
Merge pull request #14094 from kalabiyau/fix_parameters_naming

Fix parameter naming in RemoteIp middleware constructor method [ci skip]
Document the default scopes change on the release notes, CHANGELOG
and upgrating guides

[ci skip]
Fix the column name [ci skip]
Don't use `# =>` when it is not the expression values

[ci skip]
Merge pull request #14095 from rails/rm-scopes

Document `default_scope` changes
Introduce `render :body` for render raw content

This is an option for sending a raw content back to browser. Note that
this rendering option will unset the default content type and does not
include "Content-Type" header back in the response.

You should only use this option if you are expecting the "Content-Type"
header to not be set. More information on "Content-Type" header can be
found on RFC 2616, section 7.2.1.

Please see #12374 for more detail.