[BUG]: tablesFilter doesn't work when using views

I have a Postgres DB with a couple of tables and views autogenerated from my hosting service. I wish to ignore these all together. However, when I run generate and push, I get prompted "Is table created or renamed from another table?" and then a list of the views and tables.
drizzle-kit: 0.21.1
drizzle-orm: 0.30.10

Example:

In the example, spatial_ref_sys is a table and the rest is views.

Heres my config:
```JavaScript
// config.drizzle.js
import 'dotenv/config'

import { defineConfig } from 'drizzle-kit'

const DATABASE_URL =
process.env.DATABASE_URL || process.env.POSTGRESQL_ADDON_URI

export default defineConfig({
schema: 'src/db/schema.*',
out: 'src/db/migrations',
dialect: 'postgresql',
dbCredentials: {
url: DATABASE_URL,
},
verbose: true,
strict: false,
tablesFilter: [
'!geography_columns',
'!geometry_columns',
'!raster_columns',
'!spatial_ref_sys',
'!pg_stat_statements',
'!raster_overviews',
'!pg_stat_statements_info',
],
schemaFilter: ['public'],
})
```

Current workaround is to declare the autogenerated views + tables in schema as pgTable's in my schemas and manually create them in my local DB

Start with config.drizzle.js and the tablesFilter configuration used by the generate and push commands, reproducing the behavior against PostgreSQL views and tables. Verify that the listed autogenerated objects are ignored without declaring them as pgTable entries, and that the rename/create prompts no longer include them.

Written by the indexing model from the issue text.