Geometry datatype converted to varchar when applying filter to schemas disaplayed in connection tree

### Description

Hi,

I've a PostgreSQL connection in which I want to filter to keep a schema for a specific project.
In this schema, I've tables that contain spatial columns, as this example:

On the other hand, I want to apply a filter on my schemas as following:

If I apply this filter, the format of my spatial column is converted as a column with the varchar datatype, and my table is no longer considered as a spatial layer in DBeaver (i.e. no spatial tool in the data tab)

It seems to be a bug, but there is maybe an explanation and a way out to solve this problem.

Thanks in advance for your help.

Cheers,
Eric.

### DBeaver Version

Community edition Version 26.1.2.202607051737

### Operating System

Zorin OS 17.3 Core

### Database and driver

1. PostgreSQL 15.18.0
2. JDBC driver : org.postgresql:postgresql:RELEASE [42.7.11]

### Steps to reproduce

_No response_

### Additional context

_No response_

Start by reproducing the issue in DBeaver 26.1.2 with PostgreSQL 15.18 and JDBC driver 42.7.11, comparing the table metadata with and without the schema filter. The fix is done when spatial columns remain geometry and the table retains its spatial tools after filtering schemas.

Written by the indexing model from the issue text.