Merge pull request #11014 from senny/10936_inspect_does_not_crash_without_connection

`inspect` for AR model classes does not initiate a new connection.
Don't remove trailing slash from PATH_INFO for mounted apps

Previously when app was mounted as following:

    class Foo
      def call(env)
        [200, {}, [env['PATH_INFO']]]
      end
    end

    RackMountRailsBug::Application.routes.draw do
      mount RackTest.new => "/foo"
    end

trailing slash was removed from PATH_INFO. For example requesting

    GET /foo/bar/

on routes defined above would result in a response containing "/foo/bar"
instead of "/foo/bar/".

This commit fixes the issue.

(closes #3215)
Fix documents for create_join_table
Update the feedback instructions [ci skip]

Since docrails as moved from lifo/docrails to rails/docrails we have
to ask for commit rights or submit patches directly to the rails
repository
Merge pull request #11039 from robin850/patch-2

Backport #11033 to master
Saying gemcutter => rubygems [ci skip]
fix the path of action view from actionpack/lib/action_view => actionview/lib/action_view
Merge pull request #11045 from rajars2576/fixing_action_view

fix the path of action view from actionpack/lib/action_view => actionvie...
Adding verbose mode to test_with_ar_integration
Adding verbose in isolated test.
Merge pull request #11043 from arunagw/gemcutter_to_rubygems

Saying gemcutter => rubygems [ci skip]
Merge pull request #11040 from satococoa/fix-create_join_table-document

Fix documents for create_join_table [ci skip]
Merge pull request #10537 from jetthoughts/10428_bug_with_config_assets_precompile

 #10428: Added tests for config.assets.precompile
fix bad test by making number that fits for integer

PR https://github.com/rails/rails/pull/10566 had to be reverted
because after applying the fix test
"test_raise_record_not_found_error_when_invalid_ids_are_passed"
started failing.

In this test invalid_id is being assigned a really large number
which was causing following failure when PR #10566 was applied.

```
RangeError: bignum too big to convert into `long long'
SELECT  `interests`.* FROM `interests`
WHERE `interests`.`man_id` = ? AND `interests`.`id` = ?
LIMIT 1  [["man_id", 970345987], ["id", 2394823094892348920348523452345]]
```

This test is not failing in master because when test code
`man.interests.find(invalid_id)` is executed then interests
are fully loaded in memory and no database query is executed.

After PR #10566 was merged then test code
`man.interests.find(invalid_id)` started executing sql query
and hence the error.

In case someone is wondering why the second part of query is not
failing, then that's because the actual query does not require
any variable substituation where the number is large. In that
case the sql generate is following.

```
SELECT `interests`.* FROM `interests`
WHERE `interests`.`man_id` = ? AND `interests`.`id`
IN (8432342, 2390102913, 2453245234523452)  [["man_id", 970345987]]
```
Merge pull request #11049 from neerajdotname/no-need-of-large-number

fix bad test by making number that fits for integer
do not load all child records for inverse case

currently `post.comments.find(Comment.first.id)` would load all
comments for the given post to set the inverse association.

This has a huge performance penalty. Because if post has 100k
records and all these 100k records would be loaded in memory
even though the comment id was supplied.

Fix is to use in-memory records only if loaded? is true. Otherwise
load the records using full sql.

Fixes #10509
Merge pull request #11051 from neerajdotname/10509f

do not load all child records for inverse case
Remove code related to the rails test command

Remove the mention about this command in the rails command's help
message and remove the "t" alias related to it.
Merge pull request #11050 from robin850/remove-rails-test-mention

Remove code related to the rails test command
flatten merged join_values before building the joins

fixes #10669

While joining_values special treatment is given to string values.
By flattening the array it ensures that string values are detected
as strings and not arrays.