expression: support sequence function

[AilinKid]

What problem does this PR solve?

mysql> create sequence seq
Query OK, 0 rows affected (0.00 sec)

mysql> select nextval(seq)
+--------------+
| nextval(seq) |
+--------------+
|            1 |
+--------------+
1 row in set (0.001 sec)

mysql> select lastval(seq)
+--------------+
| lastval(seq) |
+--------------+
|            1 |
+--------------+
1 row in set (0.001 sec)

mysql> select setval(seq, 100)
+------------------+
| setval(seq, 100) |
+------------------+
|              100 |
+------------------+
1 row in set (0.000 sec)

What is changed and how it works?

1: support sequence function nextval, lastval, setval.
2: implement sequenceState which could be used to cache sequence lastval.
3: introduce SequenceSchema interface to do the sequence schema check in expression package. (If we use information schema, that will cause import cycle problem)

Check List

Tests

• Unit test
• Integration test

Code changes

• Has introduce SequenceSchema interface in util package.

Related changes

• Need to update the documentation

Release note

• support sequence function.

[AilinKid]

/run-unit-test

[AilinKid]

/build

[AilinKid]

/build

[crazycs520]

No test for those feature?

[AilinKid]

No test for those feature?

The sequence allcator is in next PR, the code here is the code in expression package.
The function logic test will be in the PR too (put it together will be > 500).
So it will be coming soon!

PTAL @crazycs520

[Deardrops]

Consider sync.Map and avoid use sync.Mutex manually?

[AilinKid]

Maybe the map[int64]int64 is more directly to know what kind of the k&v it is.
Sync.map will store the interface, and transform it, maybe too heavy for int64.

[Deardrops]

LGTM

[crazycs520]

LGTM

[crazycs520]

/run-all-tests

[AilinKid]

/merge

[sre-bot]

/run-all-tests