[IMPAC-745] Fixed Cash Projection Crash

[iseessel]

@cesar-tonnoir

Instead of calling update on highCharts multiple times new data is introduced, I created an entirely new chart. For some reason I could not figure out the create method is faster than the update for the highCharts API.

Because of this, I had to change the way the options were stored, as we need to put all the options in at once.

Additionally if an input was invalid, the create and cancel buttons would not go back to normal. I solved that by adding a tostr error and invoking #cancelCreateKpi. I don't know what the intended behavior was, but you could not choose a number less than 0.

I am also not entirely confident in how the options from the specific widgets is getting integrated into the highCharts factory. It seems like _.get is being used to retrieve options from the specific widgets and injecting them into the big options-hash in highcharts-factory.svc.coffee. I think this could be refactored to merely merging the specific widgets' options hash with these default options, but this would take some time. For this pull request, I followed the current patterns of merging options.

[iseessel]

@xaun

Along with your approach, I suggest we use short setter methods that take direct and specific arguments that populate the @options hash. Anything that is generated dynamically in @template will be refactored to a setter method that populates the @options hash.

[iseessel]

@ouranos Realized I was making PR onto 1.6 and not 1.6.9. This New Pull request made.

[xaun]

Moved to PR #480