Fix numericality validator to still use value before type cast except Active Record

* Call block to #redirect_to in controller context

The documentation for ActionController::Redirecting states that a Proc
argument "will be executed in the controller's context."  However,
unless #instance_eval is used (removed in 6b3ad0ca), that statement is
false for procs defined outside of the controller instance.

This commit restores the documented behavior.

Fixes #33731.

* Move test proc into a constant in another class

Per @rafaelfranca's suggestion.

[Steven Peckins + Rafael Mendonça França]

* Add documentation for `:collation` option

The table definition supports a `:collation` option for string and text columns, but this is not documented anywhere that I could find.

I'm not sure if the "If not specified" part is accurate. From [this PR](https://github.com/rails/rails/commit/1515c4d98da3f730ef971fa5a13cad828bd9bef4), it looks like it passes `nil` and lets the database handle the collation, but I'm happy to change it if I misread the code.

[ci skip]

* FIX remove whitespace

[Nate Pinsky + Rafael Mendonça França]

Update "Action View Form Helpers" guide

Follow up #33523 [ci skip]

This commit is the next work after #33523.

Also, this commit removes mention about hidden `utf8` input. Since
form helpers don't generate this input by default since #32125.

Note that I also had created PR #31972 with improvements to
"Action View Form Helpers" guide, but I'll rebase it after merging the
current PR.

Clarify example of the test [ci skip]

ActionDispatch::TestProcess::FixtureFile

Add test case to test enum in has_many

There is test in has_one to test enum, but there is no for has_many.

[Rich Chen]

Format respond_to method as code in doc [ci skip]

This updates the `respond_to` method to be code formatted rather than
plain text (as it refers to the method)

Because there are tests that fail due to the influence of the
`async_exec` deprecate message.
https://travis-ci.org/rails/rails/jobs/420345370

Related to #33188.

Handle only specifically relevant Azure HTTPErrors ActiveStorage::Service::AzureStorageService#upload and #delete

The Azure gem uses `Azure::Core::Http::HTTPError` for everything:
checksum mismatch, missing object, network unavailable, and many more.
(https://www.rubydoc.info/github/yaxia/azure-storage-ruby/Azure/Core/Http/HTTPError).
Rescuing that class obscures all sorts of  configuration errors. We
should check the type of error in those rescue  blocks, and reraise when
needed.

This reverts commit b204d167, reversing
changes made to de6a200f.

Handle only specifically relevant Azure HTTPErrors in ActiveStorage::Service::AzureStorageService

The Azure gem uses `Azure::Core::Http::HTTPError` for everything:
checksum mismatch, missing object, network unavailable, and many more.
(https://www.rubydoc.info/github/yaxia/azure-storage-ruby/Azure/Core/Http/HTTPError).
Rescuing that class obscures all sorts of  configuration errors. We
should check the type of error in those rescue  blocks, and reraise when
needed.

[ci skip] change all instances of blacklist and whitelist to denylist…

Prevent deadlocks when waiting for connection from pool.

The purpose of fe9547b6 is to work type casting to value from database.

But that was caused not to use the value before type cast even except
Active Record.

There we never guarantees that the value before type cast was going to
the used in this validation, but we should not change the behavior
unless there is some particular reason.

To restore original behavior, still use the value before type cast if
`came_from_user?` is undefined (i.e. except Active Record).

Fixes #33651.
Fixes #33686.

Follow up #33659

`Topic` isn't loaded in this test file.

Use string lengths instead of regexp to extract path

The regexp was introduced in 186ac4cd,
and looks cosmetic. While they should be functionally identical in
theory, in practice, case insensitive (but preserving) filesystems can
give results that are differently-cased from the pattern we supplied.

I don't know how to force the filesystem to do the surprising thing,
even when running in an environment that _could_, so no new test.

Omit BEGIN/COMMIT statements for empty transactions

Test `assert_no_broadcasts` failure

See `git grep "= Logger.new(nil)"`

Remove extra `:nodoc:` comment since private methods doesn't require that.

Use `say`/`error` instead of `puts`/`$stderr.puts`

Fail more gracefully from ActiveStorage missing file exceptions

[ci skip] corrects more grammar awkwardness, replacing denylist with restricted list and consistently use permitted

* Include form_with in form_helpers rails guide

* Include form_tag and form_for footnote

* Id and class attributes are not wrapped anymore

* Include note that all form_with forms are remote:true by default

* Underline most common use case of form_with is with arguments

* Form_with no longer accepts multiple hashes in form helper calls

* Review final sections

* Revert extra documentation

* Remove unnecessary link

Remove extra execution of `uniq!` on action_methods

Update ParameterFilter to yield original parameters

Execution of `to_set` below should remove duplicated elements.

Follow up #33693