bumping arel
clean up pk delclaration in `create_table`
Small typos here and there.
fix hash duping on 1.9
ask column if it is a pk
`Http::Headers` directly modifies the passed environment.

The env hash passed to `Http::Headers#new` must be in env format.
Also be aware that the passed hash is modified directly.

docs and test-cases for setting headers/env in functional tests.

Follow up to #9700.
document request simulation methods in functional tests.
Merge pull request #9716 from senny/rework_headers_functional_tests

Rework headers functional tests
`#reset_counters` verifies counter names.

Closes #9724.

Raise an `ArgumentError` when the name of the counter does not
match an association name.
Merge pull request #9731 from senny/9724_argument_error_on_reset_counters

`#reset_counters` verifies counter names.
Warning removed unused variable task_name

warning: assigned but unused variable - task_name
Fix typos and improve docs a bit [ci skip]
Merge pull request #9732 from arunagw/warning_fix_unused_variable

Warning removed unused variable task_name
Merge pull request #9686 from strzalek/cast_number_to_string_in_pg

Cast number to string in Postgres
Merge pull request #9728 from vipulnsward/fix_em_typos

Small typos here and there.
rename `Relation#uniq` to `Relation#distinct`. `#uniq` still works.

The similarity of `Relation#uniq` to `Array#uniq` is confusing. Since our
Relation API is close to SQL terms I renamed `#uniq` to `#distinct`.

There is no deprecation. `#uniq` and `#uniq!` are aliases and will continue
to work. I also updated the documentation to promote the use of `#distinct`.
Deprecate the `:distinct` option for `Relation#count`.

We moved more and more away from passing options to finder / calculation
methods. The `:distinct` option in `#count` was one of the remaining places.
Since we can now combine `Relation#distinct` with `Relation#count` the option
is no longer necessary and can be deprecated.
Merge pull request #9683 from senny/deprecate_count_distinct_option

rename `Relation#uniq` to `Relation#distinct`
Cache the association proxy object

This reimplements the behaviour of Rails 3, as I couldn't see why we
shouldn't cache the object, and @alindeman had a good use case for
caching it:

https://github.com/rails/rails/commit/c86a32d7451c5d901620ac58630460915292f88b#commitcomment-2784312
Refactored to reuse method