针对 Express4Runner.replaceDefaultOperator 覆盖基本操作符的情况，Express4Runner.addAlias的逻辑优先级存在问题

目前 operatorManager 的addOperatorAlias 方法：

public boolean addOperatorAlias(String lexeme, String operator) {

	
	BinaryOperator originDefaultOp = DEFAULT_BINARY_OPERATOR_MAP.get(operator);
	if (originDefaultOp != null) {
		BinaryOperator newOperator = adaptOriginOperator(originDefaultOp, lexeme);
		BinaryOperator prev = customBinaryOperatorMap.putIfAbsent(lexeme, newOperator);
		return prev == null;
	}

          BinaryOperator originCusOp = customBinaryOperatorMap.get(operator);
	if (originCusOp != null) {
		BinaryOperator newOperator = adaptOriginOperator(originCusOp, lexeme);
		BinaryOperator prev = customBinaryOperatorMap.putIfAbsent(lexeme, newOperator);
		return prev == null;
	}


	return false;
}

这样的逻辑在覆盖了基本操作符并且继续设置别名的时候，永远先从DEFAULT_BINARY_OPERATOR_MAP获取操作符的定义，导致不能绑定到自定义操作符方法中。例如：

runner.replaceDefaultOperator(">", new CustomGreaterCompareOperator());
runner.addAlias("大于", ">");

此时，对于 ">" 获取到的实现是CustomGreaterCompareOperator 而对于 "大于" 获取到的实现类是com.alibaba.qlexpress4.runtime.operator.compare.GreaterOperator.

是否应该对换addOperatorAlias 中的取值顺序？先从customBinaryOperatorMap中取？

Start at operatorManager.addOperatorAlias and trace how it resolves entries from customBinaryOperatorMap and DEFAULT_BINARY_OPERATOR_MAP. Reproduce the sequence using replaceDefaultOperator(">", new CustomGreaterCompareOperator()) followed by addAlias("大于", ">"), then add or run a focused test showing that the alias resolves to the customized operator.