planner: forbiden nested view creation (#15420)

[sre-bot]

cherry-pick #15420 to release-3.0

---

What problem does this PR solve?

Problem Summary:
Before this commit, nested view creation is allowed in TiDB, while select on this view brings panic. Actually, nested view creation is forbidden in MySQL.

tidb> create view v as select * from t;
Query OK, 0 rows affected (0.01 sec)                                                                                                                                    tidb> create view v2 as select * from v;
Query OK, 0 rows affected (0.02 sec)
tidb> create or replace view v as select * from v2;
Query OK, 0 rows affected (0.01 sec)
tidb> select * from v;
ERROR 2013 (HY000): Lost connection to MySQL server during query

What is changed and how it works?

What's Changed:
Check the underlying views of when creating a view. And make the error message be compatible with MySQL.

tidb> create view v as select * from t;
Query OK, 0 rows affected (0.01 sec)

tidb> create view v2 as select * from v;
Query OK, 0 rows affected (0.01 sec)

tidb> create view v3 as select * from v2;
Query OK, 0 rows affected (0.01 sec)

tidb> create or replace view v as select * from v3;
ERROR 1146 (42S02): Table 'test.v' doesn't exist

How it Works:
Forbid creating view nested.

Related changes

• Need to cherry-pick to the release branch
  release-3.0, release-3.1, release-4.0

Check List

Tests

• Integration test

Side effects
N/A

Release note

[sre-bot]

/run-all-tests

[XuHuaiyu]

/run-all-tests

[SunRunAway]

LGTM

[zz-jason]

LGTM

[sre-bot]

Your auto merge job has been accepted, waiting for 15635, 15711, 15512

[sre-bot]

/run-all-tests

[sre-bot]

@sre-bot merge failed.