Moved order of plugin setup back to pre 5.90052 location

In 17176f15aa (v5.90052) the plugin setup block was moved up to be
called immediately after setup_plugins(), however, this causes issues
with initialization order of other plugins that hook into setup(). This
commit moves the block back down to just before setup_components, where
it used to be.
Moved setup_middleware() to after plugin setup block

After moving the plugin setup block back down to its pre 5.90052
location, the setup_middleware() call also needed to be moved, now after
that block and immediately before setup_components. All tests now seem
to pass.
prep for release
fix for problem when a http style exception overloads stringification
fixed case where end action was called even if an http style exception was thrown
more docs and test cases for ENV localization
change info and version
silence warning about redefinition of variable
updated depraction notes
;
correct auto detection of terminal width and better messages about what is going on
updated changelog
test case to prove that HEAD chops off the body but not until the auto content length middleware does its thing
docs and correct middleware order
fix loading inline packages in tests
up version and uodate changelog for release
Fix spelling, grammar and structural errors in POD

- Consistently use imperative tense in Delta headers
- Fix header levels in Delta
- Consistently spell "backwards compatibility" out
- Add new and remove bogus stopwords
- Fix a handful of typos
Add Changes entry for POD fixes
Remove redundant ->setup call in t/head_middleware.t RT#95361

Now that %INC is being populated earlier and the first ->setup call
succeeds, test that and remove the the second one.
Fix test failures when running under CATALYST_DEBUG. RT#95358
Added 'autoflush' to Catalyst::Log + enabled during setup

The default logger now has an 'autoflush' flag to cause log messages to
be written immediately instead of queued. This is now set to true during
setup so that log messages show up in real time (i.e. when using the
test server).

It is currently turned back off at the end of setup for backward
compatability (specifically for Static::Simple), however, mst has
suggested that we change the API such that plugins like S::S are
responsible for turning off autoflush themselves if they need to.

See in-code comments for more details.