Feature: add ability to filter errors for `createEmptyTable` and probably other API

### SDK

Node

### Description

Side note: I'm aware of [existOk](https://lancedb.github.io/lancedb/guides/tables/#from-list-of-tuples-or-dictionaries) config option.

## Problem

Currently, when running `connect(config).createEmptyTable("example-name")`, if a table with such name already exists, the following error is thrown:

```sh
[Error: Table 'example-name' already exists] {
code: 'GenericFailure'
}
```

`GenericFailure` isn't a unique error code.
So a user is required to filter errors by error messages, which is inefficient, inconvenient, and error prone.

Start by tracing the Node SDK's createEmptyTable entry point and how the GenericFailure error is exposed to callers. Check whether related API operations use the same error path. Done means callers can distinguish an existing-table failure without matching the error message, with the intended behavior covered by tests.

Written by the indexing model from the issue text.