Typing fixes

[virus2016]

Fix for scoring types on DecayScoreFunction

[sudo-suhas]

Hey @virus2016, thanks for the PR. However, I don't think the changes you have made are correct. See https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#function-decay

The point of origin used for calculating distance. Must be given as a number for numeric field, date for date fields and geo point for geo fields. Required for geo and numeric field. For date fields the default is now. Date math (for example now-1h) is supported for origin.

So the value for origin can be number, string or a object(geo point). The same can be seen in elasticsearch source code as well.

For the other fields:

• scale: This can be either a string like 10d or a number. For date fields, this number would represent the milliseconds.
• offset: This also can either be a string or a number.
• decay: This can only be a number between 0 & 1. So changing this to number is correct.

I'd be happy to accept a PR which updates the typings and jsdoc annotations with more accurate union data types instead of *. Could you make the required changes?

[sudo-suhas]

@virus2016 could you please do the requested changes? I'd really like to merge the PR in.