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.

L’issue menziona query su tabelle con percorsi multi-livello come `db1.t1` in statement SELECT, CREATE INDEX e CREATE PROCEDURE. Cerca la logica del parser SQL e della validazione nel codebase, probabilmente in una directory come src/parser o src/sql. È necessario capire come l’engine di esecuzione gestisce attualmente il contesto del database e la risoluzione delle tabelle. La soluzione consiste nell’estendere la validazione per supportare e applicare la sintassi dei percorsi multi-livello tra i tipi di statement.

Scritto dal modello di indicizzazione a partire dal testo della issue.