tests failed due to the warnings from dependencies

[kevinjqliu]

Apache Iceberg version

main (development)

Please describe the bug 🐞

From 0.8.1 release vote devlist thread, https://lists.apache.org/thread/yy44w0l6g3smwswy7w49r9gv9h18wn22

I noticed that when running tests with latest dependencies:
- pandas==2.2.3
- pyspark==3.5.4
- getdaft==0.3.15
some tests failed due to the following warnings:

python3.11/site-packages/pandas/core/dtypes/common.py:335: DeprecationWarning: is_datetime64tz_dtype is deprecated and will be removed in a future version. Check `isinstance(dtype, pd.DatetimeTZDtype)` instead.

 python3.11/site-packages/daft/runners/pyrunner.py:344: UserWarning: PyRunner will be deprecated in v0.4.0 and the new NativeRunner will become the default for local execution.We recommend switching to the NativeRunner now via `daft.context.set_runner_native()` or by setting the env variable `DAFT_RUNNER=native`. Please report any issues at [github.com/Eventual-Inc/Daft/issues](http://github.com/Eventual-Inc/Daft/issues)

We might want to filter these warning for now

iceberg-python/pyproject.toml

Lines 899 to 910 in bfc0d9a

	# Turns a warning into an error
	filterwarnings = [
	"error",
	"ignore:A plugin raised an exception during an old-style hookwrapper teardown.",
	"ignore:unclosed <socket.socket",
	# Remove this in a future release of PySpark.
	"ignore:distutils Version classes are deprecated. Use packaging.version instead.",
	# Remove this in a future release of PySpark. https://github.com/apache/iceberg-python/issues/1349
	"ignore:datetime.datetime.utcfromtimestamp\\(\\) is deprecated and scheduled for removal in a future version.",
	# Remove this once https://github.com/boto/boto3/issues/3889 is fixed.
	"ignore:datetime.datetime.utcnow\\(\\) is deprecated and scheduled for removal in a future version.",
	]

Willingness to contribute

• I can contribute a fix for this bug independently
• I would be willing to contribute a fix for this bug with guidance from the Iceberg community
• I cannot contribute a fix for this bug at this time