S3 Tables catalog does not return a proper TableNotFound Iceberg error

[dannycjones]

Apache Iceberg Rust version

None

Describe the bug

Instead of wrapping table not found in a proper TableNotFound error, today we instead map it to an Unexpected Iceberg error with the SDK error as the source.

To Reproduce

Load a non-existent table using the s3tables catalog. I will add a test for this.

Expected behavior

I expected an Iceberg "TableNotFound" error rather than "Unexpected".

Willingness to contribute

I can contribute a fix for this bug independently