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
fix img width in guides
delegate to :class rather than 'self.class'
Improve javascript in welcome page [ci skip]
refactor Route#ast to use or-equals and block, instead of return with a cond
Merge pull request #8779 from goshakkk/refactor-route-ast

Refactor Route#ast to use or-equals and block, instead of return with a check
Refactor to not call path.ast twice
Do not call fields_for from form_for, to avoid instantiating two builders
Eliminate the usage of parent_builder option from form_for

Just use it internally from fields_for until we come up with a better solution.
Move the hidden :id field logic to where it belongs to

When dealing with nested forms, Rails automatically generates a hidden
field with the id value of the current object being generated by
fields_for. This logic was inside the method that's available from the
template object, but we just need it when really dealing with nested
attributes, so moving the code to here makes more sense.
Refactor the logic that checks whether or not to emit the hidden id field

By checking for object.persisted? first, we avoid the hash lookups for
new objects.
Merge pull request #8777 from goshakkk/delegate-class

Delegate to :class rather than 'self.class'
Move table routes formatter class to the inspector and rename it

It feels more consistent to have this class called "HtmlTableFormatter",
and to have it here with the routes inspector and console formatter,
since it's used for both routing error exceptions and the rails info
page.
Rename route_wrapper partial layout to table

It is used by the table formatter only, and it's already inside a routes
directory that namespaces it properly, so calling it just "table" seems
simpler.
Rescue from LoadError when trying to load the debugger gem for console

Avoid swallowing all exceptions that might happen when requiring
debugger, just catch a LoadError if it cannot be loaded.

Check for more background:
https://github.com/rails/rails/commit/28fd867c9bc790636d37a28f288791cd0089a6fd#commitcomment-2386952
These are already required through AS/rails

* core_ext/object/blank
* concern
* core_ext/class/attribute
* deprecation
Missing requires
Needless requires
Require 'active_support/core_ext/module/aliasing' in the infinite_comparable module
Merge pull request #8780 from diogomafra/require_core_ext

Require 'active_support/core_ext/module/aliasing' in the infinite_comparable module

When requiring 'active_support/core_ext', the following error is raised:

   undefined method `alias_method_chain' for Date:Class (NoMethodError)

Adding the missing require to this module fixes the problem.