Best Fit lightcurve results

[tylerbarna]

It would be handy to have the result.json file that's produced from lightcurve analysis to include a few extra things, namely:

• Nested key for the best fit lightcurve parameters: would include the parameter keys along with their best fit values, the best fit log likelihood, log bayes factor, the index of the best parameters in the sampling array, and anything else that might be useful.
• Another key that contains the values of the best fit lightcurve in magnitudes. This would make it easier to compare the best fit against the data it's fitting, as you currently need to call the model lightcurve object again in order to get the best fit lightcurve. Should also probably contain the associated measurement times. May be worth discussing what sampling times we would want for this: should we use the same sample times as the data that's being fit, or should we use an evenly sampled time space? The former would theoretically be better for calculating residuals and whatnot, but I can see why the latter might be preferable.

[sahiljhawar]

Sampling time is same as time used for light curve analysis

[tylerbarna]

resolved by #147