Fix test_deprecation_warning in gpuCI

[charlesbluca]

We are seeing an additional failure on test_deprecation_warning when running the GPU-enabled test on gpuCI - not sure where this is coming from, investigating on this PR

[charlesbluca]

So it looks like we're also getting a

ResourceWarning('unclosed event loop <_UnixSelectorEventLoop running=False closed=False debug=False>')

here, though I'm not sure what the cause of it is. A workaround for this would be to change the simplefilter we're using to only look out for DeprecationWarnings here, though I'm not sure if this warning should be cause for concern.

[codecov-commenter]

Codecov Report

Merging #248 (4961917) into main (3d4296b) will increase coverage by 100.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           main      #248        +/-   ##
===========================================
+ Coverage      0   100.00%   +100.00%     
===========================================
  Files         0        64        +64     
  Lines         0      2590      +2590     
  Branches      0       361       +361     
===========================================
+ Hits          0      2590      +2590     

Impacted Files	Coverage Δ
dask_sql/physical/rel/logical/values.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/custom/analyze.py	100.00% <0.00%> (ø)
dask_sql/physical/rex/__init__.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/logical/project.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/custom/drop_table.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/custom/tables.py	100.00% <0.00%> (ø)
dask_sql/physical/rex/core/input_ref.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/custom/drop_schema.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/custom/export_model.py	100.00% <0.00%> (ø)
dask_sql/physical/rel/logical/join.py	100.00% <0.00%> (ø)
... and 54 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d4296b...4961917. Read the comment docs.

[charlesbluca]

rerun tests