This is an alternative of #29722, and revert of #29601 and a1fcbd97.

Currently, association creation and normal association finding doesn't
respect `store_full_sti_class`. But eager loading and preloading respect
the setting. This means that if set `store_full_sti_class = false`
(`true` by default), eager loading and preloading can not find
created polymorphic records.

Association creation and finding should work consistently.

Since #32034, Rails 6 requires Ruby 2.4.1+.

Use lazy load hook to configure ActiveStorage::Blob

`to_prepare` callbacks are run during initialization; using one here
meant that `ActiveStorage::Blob` would be loaded when the app boots,
which would in turn load `ActiveRecord::Base`.

By using a lazy load hook to configure `ActiveStorage::Blob` instead,
we can avoid loading `ActiveRecord::Base` unnecessarily.

Update default HSTS max-age value to 1 year

Closes #32096.

`content_security_policy_nonce_generator` specifies request as an argument when calling.
https://github.com/rails/rails/blob/ddb7da8535b07f51b7a8f5e3062cc8ffbd4ff23b/actionpack/lib/action_dispatch/http/content_security_policy.rb#L100

So without this fix, will raise `ArgumentError` when start server.

Correct method documentation

Improve generated file `app/assets/javascripts/application.js` of plugin

Add `//= require rails-ujs`

Closes #32094

Fixes #31909.
Closes #31911.

The callback parameters need to reflect changes after
https://github.com/rails/rails/pull/28800

* Add test case for open-ended range.
* Add test case for numeric range for string column.

BC dates are supported by both date and datetime types.

https://www.postgresql.org/docs/current/static/datatype-datetime.html

Since #1097, new datetime allows year zero as 1 BC, but new date does
not. It should be allowed even in new date consistently.

The values infinity and -infinity are supported by both date and
timestamp types.

https://www.postgresql.org/docs/current/static/datatype-datetime.html#DATATYPE-DATETIME-SPECIAL-TABLE

And also, it can not be known whether a value is infinity correctly
unless cast a value.

I've added `QueryAttribute#infinity?` to handle that case.

Closes #27585.

Since #32028, Rails 6 requires Ruby 2.3+.
No longer needed workaround for Ruby 2.2 "private attribute?" warning.

Use `rubocop-0-52` channel

Since https://github.com/rails/rails/pull/32091 expects RuboCop 0.52.1

Update rubocop to the latest version

Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27).

Before: 131 offenses detected.

After: no offenses detected

Fix plugin generated files

- Do not generate `javascript_include_tag` if `--skip-javascript`
- Generate `<%= csp_meta_tag %>`. Related to #32018.

Remove passing extra arguments to ActiveJob Callbacks

This reverts commit 16f279eb, reversing
changes made to 6c6a30a7.

The config can be named anything, not just default (although all
generated apps will be named default). We can't just delete configs that
don't have a database because that will break three-tier configs. Oh
well.

This reverts commit 0979713a.

I originally wanted to delete the default config but found out it can
be called anything which means the code would blow up in unexpected
ways.

I thought "cool ill just delete the configs without dbs" and realized
that totally 100% breaks the three-tier config. So I'm reverting this
and the other commit.

Add support for timezones to Active Job

Add support for automatic nonce generation for Rails UJS

Properly escape column name embedded into regexp

Record what was the current timezone in effect when the job was
enqueued and then restore when the job is executed in same way
that the current locale is recorded and restored.

SQLServerAdapter (gem `activerecord-sqlserver-adapter`) uses square
brackets for quoting column names (e.g. `[id]`). Those brackets must not
be misinterpreted in regular expressions.

Failure:
Expected /SELECT [developers].[id].* FROM developers/ to match "SELECT [developers].[id], [developers].[name], [developers].[salary], [developers].[firm_id], [developers].[mentor_id], [developers].[created_at], [developers].[updated_at], [developers].[created_on], [developers].[updated_on] FROM developers".

In #32075 I deleted the default configuration since that's what's
generated with the Rails app. Since someone could change the default
name instead delete any config that doesn't have a database so we can
avoid peppering our Rails tasks with conditionals to deal with invalid
database configs.

Call methods with .method_name not ::method_name

Found several instances.

Follow up on 63d530c5

Since #30241, if namepsace is specified, routes will be generated even
if there is no actions.

However, it seems that this behavior is not intentionally added behavior.
As with 5.1, routes should not be generated if actions are not specified.

Fixes #32072.