fix(query): tuple field name can not contain special char

[TCeason]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

This bug maybe cause session panic:

create table t(d tuple("A-a" int, b int));

panicked at src/query/ast/src/parser/parser.rs:67:13:

SyntaxException. Code: 1005, Text = error: 
  --> SQL:1:27
  |
1 | CREATE TABLE tc (d TUPLE(A-a Int32, b Int32))
  | ------           - -----  ^ unexpected `-`, expecting `BOOLEAN`, `BOOL`, `UINT8`, `TINYINT`, `UINT16`, `SMALLINT`, `UINT32`, `INT`, `INTEGER`, `UINT64`, `UNSIGNED`, `BIGINT`, `INT8`, `INT16`, `INT32`, `INT64`, `SIGNED`, `FLOAT32`, `FLOAT`, `FLOAT64`, `DOUBLE`, `DECIMAL`, `ARRAY`, `MAP`, `BITMAP`, `TUPLE`, `DATE`, `DATETIME`, `TIMESTAMP`, `BINARY`, `VARBINARY`, `LONGBLOB`, `MEDIUMBLOB`, `TINYBLOB`, `BLOB`, `STRING`, `VARCHAR`, `CHAR`, `CHARACTER`, `TEXT`, `VARIANT`, `JSON`, `GEOMETRY`, or `NULLABLE`
  | |                | |       
  | |                | while parsing TUPLE(<name> <type>, ...)
  | |                | while parsing type name
  | |                while parsing `<column name> <type> [DEFAULT <expr>] [AS (<expr>) VIRTUAL] [AS (<expr>) STORED] [COMMENT '<comment>']`
  | while parsing `CREATE [OR REPLACE] TABLE [IF NOT EXISTS] [<database>.]<table> [<source>] [<table_options>]`

Modify

Modify tuple type parser.

Add a check, if tuple filed name contain char that is not alphanumeric characters, will directly return error.

• Fixes bug: tuple field with special char will cause session panic #15125

Tests

• Unit Test

Type of change

• Bug Fix (non-breaking change which fixes an issue)

[what-the-diff]

PR Summary

• Validation Added in expr.rs for Field Names
  Introduced validation for tuple field names to permit only alphanumeric characters for better consistency and accuracy in data handling.

• New Test Case in parser.rs
  Implemented a new test case to verify the functionality of creating a table where tuple fields include non-alphanumeric characters. This will help ensure the robustness of our table creation functionality.

• Error Messages Updated in statement-error.txt
  Enhanced error reporting by adding a specific error message and highlighting for invalid tuple field names when attempting to create a new table. This improvement will make troubleshooting easier and more intuitive.

[andylokandy]

Consider using failure:

Suggested change

	return Err(nom::Err::Error(ErrorKind::Other(
	return Err(nom::Err::Failure(ErrorKind::Other(