expression: fix wrong result of Not/IsTrue/IsFalse functions

[eurekaka]

What problem does this PR solve?

Fix #10443

Besides from the case mentioned in the above issue, another wrong result case is:

mysql> select '0.3' is true;
+---------------+
| '0.3' is true |
+---------------+
|             0 |
+---------------+
1 row in set (0.00 sec)

What is changed and how it works?

• For IsTrue/IsFalse, if the argument type is string or json, do not convert it to int, add new builtin function signature for string types;
• For Not, convert its evaluation to use IsFalse and IsNull;

Check List

Tests

• Unit test: will be added later
• Integration test: will be added later

Code changes

• Has exported variable/fields change
• Has interface methods change

Side effects

• Increased code complexity

Related changes

• Need to cherry-pick to the release branch

[codecov]

Codecov Report

Merging #10498 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #10498   +/-   ##
===========================================
  Coverage   81.5496%   81.5496%           
===========================================
  Files           435        435           
  Lines         94058      94058           
===========================================
  Hits          76704      76704           
  Misses        11883      11883           
  Partials       5471       5471

[eurekaka]

/run-all-tests

[eurekaka]

/run-unit-test

[lonng]

LGTM

[zz-jason]

LGTM

[sre-bot]

/run-all-tests

[zz-jason]

should we cherry pick this pr to release 3.0 and 2.1?

[sre-bot]

@eurekaka merge failed.

[zz-jason]

/run-integration-common-test

[eurekaka]

@zz-jason if we cherry-pick this PR, we need to cherry-pick commits in tipb (which has no release branch at all?) and tikv as well...

[zz-jason]

Yeah, that's a huge work.