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.

El issue menciona consultar tablas con rutas de varios niveles como `db1.t1` en sentencias SELECT, CREATE INDEX y CREATE PROCEDURE. Busca la lógica del parser SQL y de validación en el codebase, probablemente en un directorio como src/parser o src/sql. Es necesario entender cómo el motor de ejecución maneja actualmente el contexto de base de datos y la resolución de tablas. La solución implica extender la validación para admitir y hacer cumplir la sintaxis de rutas de varios niveles en todos los tipos de sentencias.

Escrito por el modelo de indexación a partir del texto del issue.