Fix warnings in tests

```
activerecord/test/cases/adapters/postgresql/range_test.rb:159: warning: (...) interpreted as grouped expression
activerecord/test/cases/finder_test.rb:38: warning: shadowing outer local variable - e
activerecord/test/cases/finder_test.rb:43: warning: shadowing outer local variable - e
```

Keep the types of virtual columns after yaml serialization

remove depricated Validatior#setup

On MySQL and PostgreSQL, the adapter does not type cast virtual columns
for us.

Fix cache_digest rake tasks

Inline PG array type casting helper

Bring cache_digests:* rake tasks up-to-date with the API changes introduced in
637bb726

This is a follow up to #15602 which rendered the guides in a weird state:

  >  You can also specify some options just after the field type between curly
     braces. You can use the following modifiers:

  >  `null`         Allows or disallows `NULL` values in the column.

  >  NOTE: `null` and `default` cannot be specified via command line.

The modifiers are now moved into a separate section. The generator
simply referes to that section.

Related to #15583.

/cc @JuanitoFatas

[ci skip] Rename: Rails Database Migration to Active Record Migration.

This will need to setup permanent redirect for the old guide.

ActiveRecord::FinderMethods.find doesn't pass proc parameter to array

Manual merge of #15584.

Closes #15584.

[ci skip] Add note about type modifiers that cannot be specified in command line.

Use HasAndBelongsToMany instead of HABTM

reuse available collection? check instead of macro

Reflection has an available method that is used to check if the
reflection is a collection. Any :has_many macro is considered a
collection and `collection?` should be used instead of
`macro == :has_many`.

add has_one? method and reuse instead of checking macro

Abstract away use of HABTM macro

By having the `:has_and_belongs_to_many` macro in the `@collection`
we are punishing `:has_many` associations because it has to allocate
the array and check the macro.

@collection is returned to `macro == :has_many` and a new reflection
class `HABTMReflection` is created to handle this case instead.

Instead of checking for `macro == :has_one` throughout the
codebase we can create a `has_one?` method to match the `belongs_to?`,
`polymorphic?` and other methods.

Before HashWithIndifferentAccess were doing deep_dup of the inner hashes
when Hash doesn't do. Now both are behaving in the same way.

This reverts commit dd3ea171 and add a
regression test.

Fixes #15418

Rename `type_cast` to `type_cast_from_database`

In some cases there is a difference between the two, we should always
be doing one or the other. For convenience, `type_cast` is still a
private method on type, so new types that do not need different behavior
don't need to implement two methods, but it has been moved to private so
it cannot be used accidentally.

Use an actual identity type in AR::Result#identity_type

We should be able to rely on this object implenting the full type
interface.

Remove workaround for non-lazy serialize in tests

Make `_before_type_cast` actually be before type cast

Integration tests are inside protected_attributes test suite.

Fixes #15496
Fixes rails/protected_attributes#35

- The following is now true for all types, all the time
  - `model.attribute_before_type_cast == given_value`
  - `model.attribute == model.save_and_reload.attribute`
  - `model.attribute == model.dup.attribute`
  - `model.attribute == YAML.load(YAML.dump(model)).attribute`
- Removes the remaining types implementing `type_cast_for_write`
- Simplifies the implementation of time zone aware attributes
- Brings tz aware attributes closer to being implemented as an attribute
  decorator
- Adds additional point of control for custom types

Remove a long gone :order option from has_one's valid_options

`serialize` is now lazy, so the workaround is no longer needed.