We just want to augment the scope level, not the frame itself, so just
copy the frame to the new scope object.

Update info on browser connection limits [ci skip]

Browsers have not been limited to two connections per host for quite
some time now. With more connections allowed, the trade-off involved in
asset host distribution isn't so clear and it becomes more important
that developers measure actual performance before and after.

this gives us an easier way to iterate the stack

The same information is stored in the `@scope` linked list, so just get
it from there.

this lets us remove the setter and make the Resource object Read-Only

We don't need to ask `scope` for the resource because we already have it
right here.

[ci skip] Modify introduction to be consistent with other guides

Closes #21121

Reload I18n.load_path in development

make generated scaffold functional tests work inside API engines

This method raises conditionally not always so we should not documment
as it always raise.

We should return when the contoller key is not present or if the
controller doesn't exist and we didn't raised an error.

Related with dc1b937d

eliminates calling `scope` in one method, pushes the other calls up one
frame.  This goes a little way towards eliminating the internal calls to
`scope`.

[ci skip] Note that each action maps to a specific CRUD operation

* set engine's route in setup
* use fixture with engine namespace

we don't really need this hash.

we need to get a grip on what `scope` actually does.  This commit
removes some of the internal calls to `scope`.  Eventually we should add
public facing methods that provide the API that `scope` is trying to
accomplish.

`prepare_params!` would raise an exception if `params` wasn't
initialized, so it must always be available.  Remove the existence
conditional from the `controller` method.

The method we called already has the conditional we need.  Just add an
else block so that we don't need two tests.

`Dispatcher` doesn't need to hold on to the defaults hash.  It only used
the hash to determine whether or not it should raise an exception if
there is a name error.  We can pass that in further up the stack and
alleviate Dispatcher from knowing about that hash.

We know in advance whether the object is a dispatcher or not, so we can
configure the Constraints object with a strategy that will call the
right method.

it isn't used.

Reference actual classes

[ci skip] Fix the AS::Callbacks terminator docs

[ci skip] Give in-depth explanation of migrations vs. seeds.rb

[ci skip] Adding a note to Action Mailer Basics documentation that Google increased its security measures

security measures so using the example for Gmail will return a “Password Incorrect” error,
and you will receive an email from Google that they blocked a sign-in attempt.  You can change
your Gmail settings or use another ESP.

I discovered this when I was testing a simple mailer example app and was just going to
use my personal Gmail account for the test.  I think it would be best to note this change
since now Gmail may not be the best option for a quick test.  I hope this saves time for other Rails
developers.  The Gmail example does show a good example of how to configure the smpt settings.

The second argument of the terminator lambda is no longer the result
of the callback, but the result lambda.

https://github.com/rails/rails/blob/3a7609e2bafee4b071fe35136274e6ccbae8cacd/activesupport/test/callbacks_test.rb#L553