[FIX] Make range query using elasticsearch inclusive of upper boundary to be consistent with other engines (but committing only to trunk as not sure if it deserves a backport)


git-svn-id: file:///var/local/code.tiki.org/tikisvn/trunk@52406 b456876b-0849-0410-b77d-98878d47e9d5
[ENH] Allow making use of elasticsearch internal capability of indexing numeric fields for range filtering without padding, and implement for numeric tracker field.


git-svn-id: file:///var/local/code.tiki.org/tikisvn/trunk@52407 b456876b-0849-0410-b77d-98878d47e9d5
tablesorter: correcting the path didn't seem to work. completely remove then add back later.

git-svn-id: file:///var/local/code.tiki.org/tikisvn/trunk@52408 b456876b-0849-0410-b77d-98878d47e9d5
tablesorter: add back version 2.17.7

git-svn-id: file:///var/local/code.tiki.org/tikisvn/trunk@52410 b456876b-0849-0410-b77d-98878d47e9d5