feat: implement pg_catalog upon local execution mode

[yezizp2012]

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.

As title, implemented pg_type/pg_namespace/pg_cast and some other rules for ddl:

1. introduce a new SysRowSeqScanExecutor to support scanning on system table, only works in local execution mode.
2. init pg_catalog schema and system tables for all new created database, and drop them when database dropped.
3. refuse to create schema with prefix pg_.
4. refuse to create any relation under pg_catalog.

todo:

1. auto enable local mode when query on pg_catalog.
2. support more system tables.

Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests
• All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

Part of #2954

[codecov]

Codecov Report

Merging #3387 (3c6501d) into main (86e7742) will decrease coverage by 0.14%.
The diff coverage is 44.39%.

@@            Coverage Diff             @@
##             main    #3387      +/-   ##
==========================================
- Coverage   73.73%   73.58%   -0.15%     
==========================================
  Files         761      766       +5     
  Lines      104506   104879     +373     
==========================================
+ Hits        77054    77175     +121     
- Misses      27452    27704     +252     

Flag	Coverage Δ
rust	73.58% <44.39%> (-0.15%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/batch/src/executor/mod.rs	75.80% <ø> (ø)
src/batch/src/executor/sys_row_seq_scan.rs	0.00% <0.00%> (ø)
src/batch/src/task/context.rs	15.38% <0.00%> (-1.29%)	⬇️
src/common/src/catalog/mod.rs	60.44% <ø> (ø)
src/frontend/src/binder/mod.rs	100.00% <ø> (ø)
src/frontend/src/binder/relation/mod.rs	87.41% <ø> (ø)
src/frontend/src/binder/relation/table_function.rs	76.41% <0.00%> (ø)
src/frontend/src/catalog/pg_catalog/pg_cast.rs	0.00% <0.00%> (ø)
src/frontend/src/catalog/pg_catalog/pg_type.rs	0.00% <0.00%> (ø)
src/frontend/src/expr/mod.rs	87.09% <ø> (ø)
... and 33 more

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[lmatz]

Scheduler and Batch execution parts LGTM!

[liurenjie1024]

Generally LGTM

[hengm3467]

@yezizp2012 @xiangjinwu Are these changes visible to users? Does it mean that in local execution mode, RisingWave supports casts, namespaces, and types exactly the same as in PG? Thanks.

[xiangjinwu]

@yezizp2012 @xiangjinwu Are these changes visible to users? Does it mean that in local execution mode, RisingWave supports casts, namespaces, and types exactly the same as in PG? Thanks.

• These changes are visible to users.
• However, we do not want to encourage users to use them. They are here to support bigger user-friendly features that are not complete yet. PostgreSQL also exposes these "internal" things to user, but practically it adds little value to normal users.
• They are not exactly the same as in PG.

[hengm3467]

@xiangjinwu Thanks for the detailed explanation! I think it makes senses that we do not disclose these details until the bigger features are completed.