* includes -> include
* "on your computer" is implied

Better explain the bug report templates [ci skip]

setup gets called from the initializer, so it happens more than once in
a test run. Trying to drop the database again after the first process is
connected is.. ineffective. And entirely pointless.

Instead, defer creating the database to start_workers -- which only
happens once, right before we start doing anything real.

* Don't swallow output -- if there is any, it's probably useful
* Wait for the process to finish
* Use IPC instead of a sleep
* No need for a pidfile

Requiring sidekiq/testing changes stuff, so we need to counteract that
after we do so.

And given its potential to confuse things, let's do it up front, at a
predictable point.

Add a "generic" bug report template

This template gives contributors a starting point to use when reporting bugs
that does not involve Active Record or Action Pack.

Binding to localhost only allows access to localhost

This will avoid the indirection of having calling id since we already
know which is the primary key column.

Also this will make explicit the behavior since it is not clear that id
gets the right primary key value and not just the value of the "id"
column.

Raise StaleObjectError if touched object is stale and locking is enabled

Fixes #19776

change test variable names and use more verbose on method

less verbose

use _read_attribute instead of send

add missing require for ArrayInquirer

[ci skip] Fix docs and guide about 'Array.wrap'

Update association_basics.md [ci skip]

 Spell out "asynchronously" instead of async in guides [ci skip]

To me it seems like this should only be the case if `autosave: true` is
set on the association. However, when implemented that way, it caused
issues with has many associations, where we have explicit tests stating
that child records are updated when the parent is new, even if autosave
is not set (presumably to update the parent id, but other changed
attributes would be persisted as well).

It's quirky, but at least we should be consistently quirky. This
constitutes a minor but subtle change in behavior, and therefore should
not be backported to 4.2 and earlier.

Fixes #19782

[Doc] Encourage users to user super to override methods.

[ci skip]

Improve documentation for uuid [ci skip]

Add information about usage `uuid` type with `reference`

Add missing require for String#strip_heredoc

This method is being used in `#xml_http_request`, but was not properly
required. This causes `NoMethodError` on projects that are doing
integration test.

[ci skip] Replace `list` with `array`

[ci skip] Update code example of Enumerable#without

IMO we shouldn't encourage users to use methods they shouldn't need to know about. As Song (in this example) inherits from ActiveRecord, we can use super here instead to get the same effect with the bonus of not knowing how active record actually implements these methods.

add active job testing section [ci skip]

[ci skip] Document running a rake command as a rails command

fix typo asser url [ci skip]

[Skip ci] Add information about :host options