Make sure :environment task is executed before db:schema:load or db:structure:load

Otherwise, if schema_format = :sql, you will see:
$ rake db:setup --trace
** Invoke db:setup (first_time)
** Invoke db:schema:load_if_ruby (first_time)
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Invoke rails_env (first_time)
** Execute rails_env
** Execute db:load_config
** Execute db:create
db_example_development already exists
db_example_test already exists
** Execute db:schema:load_if_ruby       #<-------- :environment hasn't been executed yet
** Invoke db:schema:load (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:schema:load
~/db_example/db/schema.rb doesn't exist yet. Run `rake db:migrate` to create it then try again.
Revert "Refactor passing url options via array for polymorphic_url"

Passing options as the last value in an array doesn't work with form_for.
This reverts commit 6be564c7a087773cb0b51c54396cc190e4f5c983.
Revert "polymorphic_url with an array generates a query string"

Passing options as the last value in an array doesn't work with form_for.
This reverts commit 61c8a4d926343903593a27080216af7e4ed81268.
Remove warning: `*' interpreted as argument prefix
Merge pull request #7268 from arunagw/warning-removed-small

Remove warning: `*' interpreted as argument prefix
Changing AR:CollectionAssociation#empty? to use #exists?

COUNT(*) queries can be slow in PostgreSQL, #exists? avoids this by
selecting a single record.
Merge pull request #7270 from beerlington/use_exists_for_empty

Changing AR:CollectionAssociation#empty? to use #exists?
removes usage of Object#in? from the code base (the method remains defined by Active Support)

Selecting which key extensions to include in active_support/rails
made apparent the systematic usage of Object#in? in the code base.
After some discussion in

    https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d

we decided to remove it and use plain Ruby, which seems enough
for this particular idiom.

In this commit the refactor has been made case by case. Sometimes
include? is the natural alternative, others a simple || is the
way you actually spell the condition in your head, others a case
statement seems more appropriate. I have chosen the one I liked
the most in each case.
Update changelog
Merge pull request #7140 from seamusabshere/patch-1

Make sure :environment task is executed before db:schema:load or
db:structure:load
Add CHANGELOG entry for 3c731a4ad62430100ba0b65bc966aa6dc6280c5f
Don't use `html_escape` to test the escaping
Add AS::StringInquirer#respond_to? method

Consistently with #method_missing
let ruby decompose the tuples in the iterator
Merge pull request #7272 from lexmag/string_inquirer

Add AS::StringInquirer#respond_to? method
add changelog for #7202
Merge pull request #7275 from asanghi/perform_deliveries_in_mail

add changelog for #7202
Do not include application.js if it doesn't exists

Rails were including 'application.js' to the pack when using
`javascript_include_tag :all` even there's no application.js in the
public directory.
Rearrange example output of javascript_include_tag
Merge pull request #7277 from sikachu/master-js-include-tag-fix

Do not include application.js if it doesn't exists