Merge branch 'master' into topic/constructor_rewrite
Do not rely on Data::Dumper to produce rolled out hashrefs
Remove test cruft forgotten after 52864fbd
Clarify result_class tweaking on active/cached cursors

We need this to simplify logic of result_class type caching
Scale back validation of the 'as' attribute (revert 95e41036)

It turned out that users employ invalid-but-sensical inflation maps in
production. Remove the early sanity check of the infmap and move the code
throwing an exception all the way back to ::Row

Follow through this thread for more details:
http://lists.scsys.co.uk/pipermail/dbix-class/2013-February/011115.html
BAIL_OUT stops the entire test run - do not want that
MOAR optimization - tracking is_new_res is double work

We can get the root node assembler to do that for us instead

Also remove more of the superfluous ||= assignments
An underdefined root has to use the %cur_row_ids container

Otherwise we are polluting $cur_row_data with the extra "virtual id column"
value, and may end up stashing it back on iterative cursor parsing
Simplify more - remove loop and cleanup the while cond
Remove some superfluous expensive try blocks

We already know that the relationship exists, and ->related_source without
a schema returns undef anyway
Rename some private methods/attributes to align with what they do

No functional changes, just a s///
Forgotten cruft after 52864fbd5
Still do null-branch pruning when we are using our own inflate_result()

52864fbd was too aggressive in removing stuff - inheritance no longer
matters, but which method we will be calling does. If we are still using
our own inflate_result() there is no point of doing the double work of
blessing and then skipping null branches.
Move CDBI code out of the main ResultSet implementation
Warn in case of iterative collapse being upgraded to an eager cursor slurp
Consider unselected order_by during complex subqueried prefetch

Augment _resolve_aliastypes_from_select_args to collect the column names
it sees, allowing it to replace _extract_condition_columns() entirely.

In the process fix a number of *incorrect* limit_dialect tests
There is no point of ordering the insides of a complex prefetch without a limit
augh