Bug(frontend): referring non-existing table triggers `segv` in playground mode

Describe the bug

UPDATE Seems like all reference to non-existing table results in segv, is it intended behavior? Minimal example:

dev=> select * from t;
SSL SYSCALL error: EOF detected
The connection to the server was lost. Attempting reset: Failed.

As titled, example:

dev=> create table t (v1 int);
CREATE_TABLE
dev=> create index idx1 on t1(v1);
SSL SYSCALL error: EOF detected
The connection to the server was lost. Attempting reset: Failed.

Error message in bash:

/var/folders/ys/crdc7hkd6xl1450fdkzvwgfh0000gn/T/fsio_9YSFr84Yk0.sh: line 5: 66968 Segmentation fault: 11  RUST_BACKTRACE=1 RW_NODE=playground cargo run --bin risingwave --profile "${RISINGWAVE_BUILD_PROFILE}"

Interestingly the deployment mode doesn't have this issue.

To Reproduce

No response

Expected behavior

dev=> create table t (v1 int);
CREATE_TABLE
dev=> create index idx1 on t1(v1);
ERROR:  QueryError: Catalog error: table not found: t1

Additional context

No response