Allows any Rake task to be run through `bin/rails` such as `bin/rails db:migrate`,
`bin/rails notes` etc.

The Rake tasks are appended to Rails' help output, and blend in as standard commands.

Prevent a 500 in the default controller scaffold

Update web-console to 3.0.0

The API isn't ready yet, which means we haven't documented it.

People can't make their own commands, so there's no reason to show it
in generated documentation.

If you update a record with no attributes, you'll hit a 500 from a guard
in `assign_attributes` raising:

```ruby
ArgumentError: When assigning attributes, you must pass a hash as an argument.
    app/controllers/users_controller.rb:44:in `block in update'
    app/controllers/users_controller.rb:43:in `update'
    test/controllers/users_controller_test.rb:37:in `block in <class:UsersControllerTest>'
```

Not a biggie, but may be quite confusing for the folks new to the
framework.

Fix paintIt method in JavaScript guides [ci skip]

See the rationale in the comment present in this patch.

Before this commit, the sole presence of the Listen constant
enabled the evented file watcher (unless listen resorted to
the polling backend).

This way, applications may depend on listen for other stuff
independently of this feature. Also, allows teams with mixed
setups to decide at boot time whether the evented watcher
should be enabled for each particular instance.

Web Console 3.0.0 is compatible with Rails 5, while the 2.x.x releases
aren't.

Tiny typo in the testing guide; articules should be articles.

- Changed "paintIt" to "@paintIt" so that it can be called in an on
  click handler.
- Closes #22568

Use adapter supports_datetime_with_precision

So that it appears correctly in the CHANGELOG on github.

In Rails 5.1 `ActionController::TestCase` will be moved out of Rails
into it's own gem.

Please use `ActionDispatch::IntegrationTest` going foward.

Because this will be moved to a gem I used `# :stopdoc:` instead of
deleting the documentation. This will remove it from the Rails
documentation but still leave the method documented for when we move it
to a gem.

Guides have been updated to use the routing structure used in Integration
and all test examples have been updated to inherit from
`ActionDispatch::IntegrationTest` instead of `ActionController::TestCase.

Fixes #22496

Show redirect response code in assert_response messages

This reverts commit c2e70ca9, reversing
changes made to b0e5fc27.

this broke the build

Follow-up to PR #19977, which helpfully added the redirection path to the error message of assert_response if response is a redirection, but which removed the response code, obscuring the type of redirect.

This PR:

- brings back the response code in the error message,

- updates the tests so the new messages can be tested,

- and adds test cases for the change.

Remove unused deprecation notice

Use assert over assert_predicate in assert_response

fix links to code of conduct [ci skip]

CoC text has been moved to the Rails website in 90bcb6de

Correct the time comparison for remember_me token

Corrects the time comparison to be `Time.now < time` which allows the user to
be set only when the current time is less than the 2 week window given in the
example.

Update nokogiri to 1.6.7

This picks up https://github.com/sparklemotion/nokogiri/pull/1218
which allows nokogiri to compile on Xcode-only OS X systems.

Adding Enums section to AR Querying. [ci skip]

show relative path the rerun snippet of test runner in rails engine

Since the absolute path is not required to re-run the test,
modified so that unnecessary information is not displayed.

```ruby
# before
bin/rails test /path/to/blorgh/test/integration/navigation_test.rb:5

# after
bin/rails test test/integration/navigation_test.rb:5
```

Fixed typo in mysql client parameter

Rails API: Ability to return error responses in json format also in development

We don't need to set config.debug_exception_response_format given that :api is the default value for only API apps

I did this change but it is affecting how the request params end up
after being processed by the router.

To be in the safe side, I just take the format from the extension in the
URL when is not present in those params and it's being used only for the
`Request#formats` method