fix(frontend): occasional table v2 create error

[BugenZhao]

What's changed and what's your intention?

This PR ensures that the base table is created before creating the associated materialized view.

Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

Close #230.

[codecov]

Codecov Report

Merging #267 (816ccbe) into main (f69f5f6) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main     #267      +/-   ##
============================================
- Coverage     74.07%   74.06%   -0.01%     
  Complexity     2665     2665              
============================================
  Files           850      850              
  Lines         48119    48124       +5     
  Branches       1583     1584       +1     
============================================
  Hits          35643    35643              
- Misses        11666    11671       +5     
  Partials        810      810              

Flag	Coverage Δ
java	61.94% <0.00%> (-0.03%)	⬇️
rust	79.31% <0.00%> (ø)

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

Impacted Files	Coverage Δ
...singwave/execution/handler/CreateTableHandler.java	0.00% <0.00%> (ø)
rust/storage/src/table/simple_manager.rs	83.58% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f69f5f6...816ccbe. Read the comment docs.

[skyzh]

I would still recommend returning an Error instead of panic. If we panic, the thread would hang, and the e2e test will never end (until reaching timeout)

[BugenZhao]

I would still recommend returning an Error instead of panic. If we panic, the thread would hang, and the e2e test will never end (until reaching timeout)

Okay. Let's make it temporarily an error to see whether this PR really fix this problem :). Considering the inexistence of associated base table is an unrecoverable error, it should be a panic in the future.