Fix timeout property data type in ClientConfig for Deltalake.

[edsoncezar16]

Summary & Motivation

The current implementation of ClientConfig expects the timeout parameter to be an int.

However, this leads to errors when using the io manager, for instance, to load an input:

dagster._core.errors.DagsterExecutionLoadInputError: Error occurred while loading input "xxx" of step "xxx": 

...

The above exception was caused by the following exception:OSError: Generic Config error: failed to parse "120" as Duration 

According to this discussion in the deltalake community, the expected format for this parameter is a string like "120s".

How I Tested These Changes

Running locally with a modification to the DeltalakeDbClient to make the proposed modification effective I was able to use the parameter without the aforementioned error:

class CustomDeltaLakeDbClient(DbClient):
    @staticmethod
    @contextmanager
    def connect(context, table_slice: TableSlice) -> Iterator[TableConnection]:
        
        ...

        storage_options = {
            **{k: str(v) for k, v in storage_options.items() if v is not None},
            **{k: str(v) for k, v in client_options.items() if v is not None},
        }
        # fix timeout setup
        if "timeout" in storage_options:
            storage_options["timeout"] += "s"

        ...        

[garethbrickman]

cc @ion-elgreco for sanity check

[ion-elgreco]

cc @ion-elgreco for sanity check

I don't maintain the dagster-deltalake, only dagster-delta (https://github.com/ASML-Labs/dagster-delta)