Check if table id exists.

This operation should behave exactly like DescribeTable, except it does not contain a response body.

REST NAMESPACE ONLY REST namespace conveys the result through the HTTP status code with no response body. The REST response maps to the TableExistsResponse model as follows:

• a 200 response means the table exists; a 404 response means it does not
• response headers map to context via the header. prefix (see the Context schema)

For DirectoryNamespace implementation, a table exists if either:

• The table has Lance data versions (regular table created with CreateTable)
• A .lance-reserved file exists in the table directory (declared table created with DeclareTable)

{
  "identity": {
    "api_key": "api_key",
    "auth_token": "auth_token"
  },
  "context": {
    "key": "context"
  },
  "id": [
    "id",
    "id"
  ],
  "version": 0
}