Correct a bug where ignored questionnaires where not ignores without ignored filters on ChartController
Export expected estimations (/browse/table/country data)
Support comma in country names
Some countries didn't have geoname, leading to crash when computing
Relation country-geoname should not use two foreign keys

We used to have duplicated foreign keys in both tables. This was clearly
unnecessary and error prone.

In addition we made Geoname mandatory for Countries
Caches were not hit if there was no result #2358

When mass fetching from DB but didn't get any result, any subsequent call
missed the cache, and attempted to re-fill the cache. This lead to extremely
poor performance for a questionnaire without any Rule (such as the one created
via /browse/chart)
Do not set file permissions automatically

This breaks local installs and Travis. It should only be done in the specific
environnement of production
Refactor create question in QuestionController
New JMP data should be computed up to 2012 #2360
Consider #DIV/0! as null values for expected results #2360

Grenada has several computation errors in Excel file. While those error
should be avoided from the first place, we can safely assume that their
semantic is an absence of values, hence NULL.
Use __METHOD__ for more complete logs #2360
Detect hardcoded expected results #2360
Cover regression formula syntax with unit tests #2360
Implement hierarchic filter::getList() using Trait FlatHierarchy and adapt questionController to use the same trait.
Surface water should fall back on later year result #2360

Our custom syntax did not allow to refer to another year result, hence
Surface water incorrectly did no fall back on next year result, leading
to NULL values, whereas it should have extended all the way back to first year.
Other Improved should be computed even if POP is absent #2360
Replace hardcoded complementary total with formula #2360

We used to hardcode the fact that high filters results for total part
was the sum of other parts. However, this is not always the case. By moving
this kind of behavior to Rule's formulas, we simplify our codebase while
giving enough flexibility to fullfill all use cases.

In particular this allow us to get correct results for Afghanistan.s
Extend regression in the past #2360

Forgot a cases present in Excel files where regressions should be
extented into the past if the value is either 0 or 1. This fixes
mistakes for both Bangladesh and Afghanistan
Special cases for high filter rules #2360

Several countries have special cases requiring different set of rules.
It's mostly for when data is only available for one of the three parts.
Those rules are now implemented when importing (hardcoded on country basis).
Better output description #2360