refactor the naming within plugin new generator

Having a method called `full?`, which checks on :full and :mountable
is very confusing. I renamed `full?` to `engine?` and created a `full?`
method that only checks the `:full` option
Refactoring the token_and_options method to fix bugs

Adding a test for the equal trun bug

Adding a test for the after equal trunc bug

Adding a test for the slash bug

Adding a test for the slash quote bug

Adding a helper method for creating a sample request object with token

Writing a method to create params array from raw params

Writing a method to rewrite param values in the params

Writing a method to get the token params from an authorization value

Refactoring the token_and_options method to fix bugs

Removing unnessecary test

A constant for this shared regex seemed appropriate

Wanting to split up this logic

Adding small documentation pieces
Add script_name option description and example for #url_for options
Explain controller specific assets more thoroughly

The current section on controller specific assets does not really explain how the default application.css and application.js files
generated by rails will work with controller specific assets and is a bit ambiguous. We should remind users that they will be included
into their application by default but that they have the option to include them only where needed if they want and how this works with
precompiling assets.

[ci_skip]
attempt to fix slow runner name method
Move changelog entry to the top [ci skip]
Merge pull request #8559 from mshytikov/runner_method_is_slow_with_thread_safe

Attempt to fix slow runner name method
Fix: documentation for String#humanize
Integrate Journey into Action Dispatch

Move the Journey code underneath the ActionDispatch namespace so
that we don't pollute the global namespace with names that may
be used for models.

Fixes rails/journey#49.
Remove obsolete Hash extension needed for Ruby 1.8.x support

[ci skip]
Remove the actual extension file as well [ci skip]
remove code for Ruby 1.8.x support
:nodoc: Journey because is not part of the public API [ci skip]
Merge pull request #8565 from frodsan/wed_code_journey

nodoc Journey and remove unneeded Ruby <1.9 validation
Improve AMo changelog example to not rely on AR [ci skip]
Fix Action Mailer changelog indenation to match other changelogs

Also some minor improvements to other changelogs. [ci skip]
change spy of  after invoked controller action. because ruby-2.0.0 waned unused variables
Remove Reference to Ruby 1.8.7
Prevent callback from being set twice.

When you add one callack in two separate `set_callback` calls - it is
only called once.

When you do it in one `set_callback` call - it is called twice.

This violates the principle of least astonishment for me. Duplicating
callback is usually an error. There is a correct and obvious way to do
anything without this "feature".

If you want to do

    before_save :clear_balance, :calculate_tax, :clear_balance

or whatever, you should better do

    before_save :carefully_calculate_tax

    def carefully_calculate_tax
      clear_balance
      calculate_tax
      clear_balance
    end

And this even opens gates for some advanced refactorings, unlike the
first approach.

My assumptions are:

- Principle of least astonishment is violated, when callbacks are either
  prevented from duplication, or not.
- Duplicating callbacks is usually an error. When it is intentional -
  it's a smell of a bad design and can be approached without abusing
  this "feature".

My suggestion is: do not allow duplicating callbacks in one callback
call, like it is not allowed in separate callbacks call.
Fix documentation style