* add a few stmt_ interface declartion

* add taos_load_table_info

* add taos_set_config(() interface

* add more interfaces

* warn 'reset query cache' only since lack engine support

* update taos-tools

* restore .gitmodules

* Revert "[TD-13408]<test>: move tests out"

This reverts commit f80a4ca49ff37431bc0bc0dafb5ccf5858b00beb.

* revert f80a4ca49ff37431bc0bc0dafb5ccf5858b00beb

* immigrate file change from stand-alone repo to TDengine

for 3.0

* remove tests repository for Jenkinsfile2
Co-authored-by: Ntangfangzhi <fztang@taosdata.com>

* [TD-13408]<test>: move tests out

for 3.0 branch

* add Jenkinsfile2
Co-authored-by: Ntangfangzhi <fztang@taosdata.com>

add getVariable() to util/sql.py

add 4 testcases to query/queryWildcardLength.py

add getVariable() to util/sql.py

add 4 testcases to query/queryWildcardLength.py

leave a uncorrelated bug ---> TD-5918

add method in util/sql.py---getColNameList() and checkColNameList

add testcase query/queryCnameDisplay.py

* [TD-4752]<feature>: python connector support nanosecond.

* [TD-4752]<feature>: support nanosecond in test framework.

return integer for nanosecond in connector since python does not support nanosecond yet.

By this commit, It will close TD-3639.

It will not require test case to write *correct* datetime string to pass
a test case. One test could use seconds, milliseconds or microseconds to
check data.

That means the three tests are equivalent:

```python
.checkData(0, 0, "2020-01-01 00:00:00")
.checkData(0, 0, "2020-01-01 00:00:00.000")
.checkData(0, 0, "2020-01-01 00:00:00.000000")
```
Co-authored-by: NHuo Linhe <linhehuo@gmail.com>

By this commit, It will close TD-3639.

It will not require test case to write *correct* datetime string to pass
a test case. One test could use seconds, milliseconds or microseconds to
check data.

That means the three tests are equivalent:

```python
.checkData(0, 0, "2020-01-01 00:00:00")
.checkData(0, 0, "2020-01-01 00:00:00.000")
.checkData(0, 0, "2020-01-01 00:00:00.000000")
```