test: add test for `con.create_table(..., database=<tuple>)`

[NickCrews]

Is your feature request related to a problem?

It looks like we have a test for con.create_table(..., database=<str>):

ibis/ibis/backends/tests/test_client.py

Line 1606 in 1de88cb

def test_insert_with_database_specified(con_create_database):

but not for when database is a tuple.

Because we aren't testing it, there are bugs in implementations, such as this one in MySQL: #11976

We should add this test (marking any failing backends as xfail) and then the above PR is ready to be merged.

Describe the solution you'd like

Add another test that is very similar to the existing test_insert_with_database_specified test, except it uses a database tuple. It will have to be marked as not_yet for all the backends that don't support the two levels of heirarchy (catalog, database).

[ShwetankShukla01]

import pytest
import ibis
from ibis.backends.tests.base import BackendTest

@pytest.mark.notyet(
["sqlite", "duckdb", "mysql", "postgres"],
reason="Backend does not support catalog + database hierarchy",
)
def test_insert_with_database_tuple(con_create_database):
con = con_create_database

# Example catalog + database
catalog = "test_catalog"
database = "test_db"
db_tuple = (catalog, database)

table_name = "test_table_tuple"

schema = ibis.schema(
    {
        "id": "int64",
        "value": "string",
    }
)

# Create table with tuple database
table = con.create_table(
    table_name,
    schema=schema,
    database=db_tuple,
)

# Insert data
data = ibis.memtable(
    [
        {"id": 1, "value": "a"},
        {"id": 2, "value": "b"},
    ]
)

con.insert(table_name, data, database=db_tuple)

# Fetch and validate
result = con.table(table_name, database=db_tuple).execute()

assert len(result) == 2
assert set(result["value"]) == {"a", "b"}