Fix solve the issue in SQL where the < operator is mistakenly recogni…

[shallowShark123]

…zed as <@ when used jointly with user-defined variables.
In SQL, <@ is a special binary operator. However, in MySQL parsing, if a space is added between < and @, MySQL will report a parsing error when executing. This means that '<@' does not need to be identified separately in MySQL as LT_MONKEYS_AT type.
In addition, when the < operator is mixed with user-defined variables, the token type identified by the current lexical parsing is incorrect.
For example:
select * from aaa where id > @sid
The correct identification method is that @sid is a user-defined variable, and the id field is compared with the variable using the binary operator >.
Current identification method:

@ is identified as the binary operator Array_ContainedBy, which is incorrect.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

刘强 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

刘强 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}