feat: support and validate query table with multiple-levels path

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

There are some problems when users try to query a table named by multiple levels.
For example, given a statement like: `SELECT col1, col2 from db1.t1;`. We are expecting:
- there is a table `t1` under database `db1`
- the current execute-engine is running on database `db1`

Similar rules should be applied on `CREATE INDEX ... `, `CREATE PROCEDURE ... ` and other statements as well

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

The issue mentions querying tables with multi-level paths like `db1.t1` in SELECT, CREATE INDEX, and CREATE PROCEDURE statements. Look for SQL parser and validation logic in the codebase, likely in a directory like src/parser or src/sql. Need to understand how the execution engine currently handles database context and table resolution. The solution involves extending validation to support and enforce the multi-level path syntax across statement types.

Written by the indexing model from the issue text.