Fix inconsistent usage of ScriptScoreFunction in FiltersFunctionScoreQuery

This commit fixes inconsistencies in `function_score` and `filters_function_score`
using scripts, see issue #3464

The method 'ScoreFunction.factor(docId)' is removed completely, since the name
suggests that this method actually computes a factor which was not the case.
Multiplying the computed score is now handled by 'FiltersFunctionScoreQuery'
and 'FunctionScoreQuery' and not implicitely performed in
'ScoreFunction.factor(docId, subQueryScore)' as was the case for 'BoostScoreFunction'
and 'DecayScoreFunctions'.

This commit also fixes the explain function for FiltersFunctionScoreQuery. Here,
the influence of the maxBoost was never printed. Furthermore, the queryBoost was
printed as beeing multiplied to the filter score.

Closes #3464
add boost_mode to rest interface

allow user to set combine functions explicitely via boost_mode variable.
make mult default boost mode

always multiply query score to function score. For script score
functions, this means that boost_mode has to be set to `plain` if
'function_score' should behave like 'custom_score'
format code
make GeoPoint parsable in lat/lon json format
add more combine functions and rename PLAIN to REPLACE
rename 'total' to 'sum', both enum and for query
Add offset to decay function score

Docs within the offset will be scored with 1.0, decay only starts after
offset is reached.
rename scale_weight -> decay
rename reference -> origin
format code
add builders for nicer java api

This commit and the previous 10 commits close issue 3533.

Closes #3533
add additional method for setting combine mode with CombineFunction parameter