Previously, with pruning set to 1 and the option k_order_solver, the
fields like dr.ghu were not set in k_order_pert, even at order=1. But
stoch_simul tries to use them to display the decision rules. Similarly
for order 2. The respective setting of the decision rule fields is now
moved to the respective cases and always conducted at order 1 and
conducted at order 2. This avoids crashes if decision rules of
theoretical moments are requested.

Conflicts:
	matlab/reports/@series/series.m
	matlab/reports/@series/write.m

In the rare combination of k_order_solver, pruning, and order=1 the steady state was not subtracted from the starting values when doing simulations

The commit moves the creation of results tables, both the ones displayed
and printed to LaTeX, from dynare_estimation_1.m to a separate function.
This factorization later allows to use this function to display results
from other estimation routines. At the same time, it removes the display
of t-statistics for posterior estimates ( #339 )

With a previously set loglinear option, both k_order_pert and
stochastic_solvers at order>1 transformed the first order solution, but
kept the higher order terms untransformed. Now, both functions output an
error.

Currently, all stochastic solvers put the error code to info(1) and use
print_info to output the error. The only exception was k_order_pert,
which immediately created an error. Thus, the use of k_order_pert did
not allow for continuing after encountering errors, because only
print_info obeys the noprint-option. Replacing mexErrCheck by setting
info should deliver the correct behavior.

This reverts commit 2815d5fb.

For parallel computations, the relative path is necessary.

-) estimation options for data set must be given also when ppost=1 (fix in testsuite);

Previously, the strings were concatenated, rendering calls to strmatch
wrong. Changed to cell arrays on which strmatch operates.