[Enhancement] Refactor reservedSymbolTable table.

[penghuo]

In OpenSearch SQL PR #1456, the reservedSymbolTable is used to store reserved symbols, such as _id. We need to explore a better approach to represent reserved symbols and examine the relationship between the reservedSymbolTable and the regular symbol table.

[acarbonetto]

Discussion tracked from #1456 (comment)

Should we include _id (and any other available reserved field) on a SELECT * FROM table request to OpenSearch?

I'd argue that we don't want this for the following reasons:

1. Practically speaking, returning reserved fields would adversely affect a large number of IT tests and existing use cases.
2. It would increase the response size unexpectedly, since reserved fields are not expected to return for all calls.
3. Semantically, the table definition does not contain these fields and SQL connectors wouldn't expect anything beyond the table definition to return on wildcard requests. In other words, SELECT * should only return fields listed in the table definition.
4. Conversely, the table definition for all tables based on OpenSearch indices should include the _ reserved words.

[acarbonetto]

Go with two abstractions for this, and projectoperator gets only the necessary list from the table.