rename xgboost to ant_xgboost

[Yancey0623]

a part work of #758

[sperlingxx]

So far, ant-xgboost is nothing but another wrapper of xgboost. Maybe we just keep the xgboost name rather than change it to ant-xgboost? I'm afraid using ant-xgboost will make user confuse about the difference bewteen ant-xgboost and xgboost, which is unnecessary in respect of users.

[Yancey0623]

So far, ant-xgboost is nothing but another wrapper of xgboost. Maybe we just keep the xgboost name rather than change it to ant-xgboost? I'm afraid using ant-xgboost will make user confuse about the difference bewteen ant-xgboost and xgboost, which is unnecessary in respect of users.

It seems that ant-xgboost is a forked branch of xgboost , the existing codegen_xgboost.go would generate a Python program which call laucnher module of ant-xgboost instead of the XGBoost Python API.

And ant-xgboost also includes many excellent features such as auto-train, launch the distributed job on k8s/spark with the launcher module. Maybe we need to let users/developers know if they are using xgboost or ant-xgboost.