`using_match_shorthand?` doesn't need to know that an options hash
exists.  Also use this opportunity to make the boolean logic a little
more sane

this simplifies the "downstream" logic since we know we'll only be
dealing with one particular type

I think we can find the original place where `action` is added to the
options hash now.

we want to try to pull this logic up to where the user actually passed
in "controller" so that it's close to the related call.  That way when
we're down the stack, we don't need to wonder "why are we doing this?"

Parametrize break sequence for word_wrap on ActionView Text Helpers

Sometimes you need a specific break sequence while using word wrap and as today the only option we have is "\n" and is hardcoded.

With this change you will be able to specify any break sequence ("\r\n" for example) as an option.

adding proper documentation for break_sequence in ActionView::Helpers::TextHelper.word_wrap

adding some more documentation for word_wrap custom break sequence and making sure we use new hash syntax

fix comment about which mail headers are excluded

[ci skip] Fix broken link markup

Dont try to call method missing in routes if thats not what we want

Add method to run command-line db apps

Conflicts:
	activerecord/CHANGELOG.md

use correct DB connection for generated HABTM table

Outdated information about session storage updated [ci skip]

Deprecate si prefix

There are some cases where :path is nil on option and we should respect
that.

We already know how to handle `path`, so lets just handle it on our own.

All callers of `action_path` interpolate the return value in to a
string, so there is no need for the method to to_s it.  to_sym on a
symbol will return the same symbol, though I think `action_path` may
always be called with a symbol so this might not be necessary.

we only need to check for `path` once.

[ci skip] Add link to testing guide

Make assert_enqueued_with and assert_performed_with returns the matched job

Now we can see where `defaults` options originate

since `controller` and `controller_scope` were the same, just combine
them

This method isn't used internally, isn't tested, isn't documented.  We
should delete it.

add a predicate method so that we can avoid is_a? calls on the resource
object.

calling `scope` isn't cheap, so try to call cheaper methods that do the
same thing for those particular parameters (in this case `path_scope`)

`resource_scope` should just put resource scopes on the stack, and
doesn't need to know what a `scope_level` is.

We just want to augment the scope level, not the frame itself, so just
copy the frame to the new scope object.

If, doing a test like this:

```
class BugTest < ActionView::TestCase
  def test_foo
    omg
  end
```

Will raise with:
```
RuntimeError: In order to use #url_for, you must include routing helpers
explicitly. For instance, `include
Rails.application.routes.url_helpers`.
```

Thats a bit confusing, as we are not calling url_for at all.