EvalStatement uses Integer instead of Long for numbers

[kortemik]

Describe the bug

EvalStatement uses Integer instead of Long for numbers

%dpl

| makeresults count=1
| eval number=6777888999

throws

java.lang.NumberFormatException: For input string: "6777888999"
	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.base/java.lang.Integer.parseInt(Integer.java:652)
	at java.base/java.lang.Integer.parseInt(Integer.java:770)
	at com.teragrep.pth_10.ast.commands.evalstatement.EvalStatement.visitEvalNumberType(EvalStatement.java:2810)
	at com.teragrep.pth_10.ast.commands.evalstatement.EvalStatement.visitEvalNumberType(EvalStatement.java:82)
	at com.teragrep.pth_03.antlr.DPLParser$EvalNumberTypeContext.accept(DPLParser.java:15917)
	at com.teragrep.pth_03.shaded.org.antlr.v4.runtime.tree.AbstractParseTreeVisitor.visitChildren(AbstractParseTreeVisitor.java:46)
	at com.teragrep.pth_03.antlr.DPLParserBaseVisitor.visitL_evalStatement_evalNumberType(DPLParserBaseVisitor.java:475)
	at com.teragrep.pth_03.antlr.DPLParser$L_evalStatement_evalNumberTypeContext.accept(DPLParser.java:15315)
``
 
**Expected behavior**
should work for numbers less than Long.MAX_VALUE just nicely
 
**How to reproduce**
use the query
 
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
 
**Software version**
10.4.0
 
**Desktop (please complete the following information if relevant):**
 - OS: <!-- [e.g. iOS] -->
 - Browser: <!-- [e.g. chrome, safari] -->
 - Version: <!-- [e.g. 22] -->
 
**Additional context**
<!-- Add any other context about the problem here. -->