Fix type casting to Decimal from Float with ...

When I defines large precision column at RDBMS,
I assigns float value, raise ArgumentError (precision too large).
Generating stubs for helper tests is overly specific. Most helpers should simply be tested as part of the view thats using them. If you need something beyond that, you can add a test yourself for them
Change the production log level default from :info to :debug. All production apps I have ever worked with has done this. Let us reflect that default. You often want those SQL quieries to be able to debug issues in production
Stubs are no longer generated for helpers, so dont test for it
Update docs to reflect that helper stubs are no longer generated
A few more tests asserting the presence of helper test stubs
Using no_result_var in Journey's parser generator

Previously the generated parser had an intermediate local variable
`result` that really useful if you're building up a stateful object but
Journey always discards the result argument to the reduce functions.

This produces a simpler parser for anybody who actually wants to read
the thing.

Sadly, there's no real performance speedup with this change.
Merge pull request #16386 from JackDanger/journey-no-result-var

Using no_result_var in Journey's parser generator
Pull in the custom configuration concept from dhh/custom_configuration
Merge branch 'master' of github.com:rails/rails
Add suggestion as to how you can app the the assets load path
Explain why we use asset digests, not what a setter does
Merge pull request #16333 from joker1007/fix_decimal_cast_from_float_with_large_precision

Fix type casting to Decimal from Float with large precision

Conflicts:
	activerecord/CHANGELOG.md
Regenerate sid when sbdy tries to fixate the session

Fixed broken test.

Thanks Stephen Richards for reporting.
fix nested `has many :through` associations on unpersisted instances

If we have
```
class Post < ActiveRecord::Base
  has_many :books, through: :author
  has_many :subscriptions, through: :books
end

class Author < ActiveRecord::Base
  has_one :post
  has_many :books
  has_many :subscriptions, through: :books
end

class Book < ActiveRecord::Base
  belongs_to :author
  has_many :subscriptions
end

class Subscription < ActiveRecord::Base
  belongs_to :book
end
```

then if `post` is not persisted, e.g `post = Post.new`, then
`post.subscriptions` will be empty no matter what.

In contrast if `post` is persisted,
e.g if `post = Post.create!` then `post.subscriptions` works as
expected.

This property could be considered even more unusual since
associations in general, work on records that are not persisted.

e.g if
```
class Post < ActiveRecord::Base
  has_many :subscriptions, through: :author
end
```

then `post.subscriptions` works as expected in all of the
above cases.