fix(typegen): python schemas exclusions

[avallete]

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

[avallete]

Looking up why the filter was needed I've found that we indeed need to filter over types based on included schemas (because for them we include all system schemas conflicting with user provided filters). The other places are filtered at introspection level.

[avallete]

note

This is the only place where the inclusion/exclusion filters from the user are bypassed and must be manually applied. Matching typescript generation:

postgres-meta/src/server/templates/typescript.ts

Lines 89 to 96 in a1c6903

	if (type.schema in introspectionBySchema) {
	if (type.enums.length > 0) {
	introspectionBySchema[type.schema].enums.push(type)
	}
	if (type.attributes.length > 0) {
	introspectionBySchema[type.schema].compositeTypes.push(type)
	}
	}

[soedirgo]

LGTM, but just confirming that this is only for perf, there's no bug on the target PR? Nvm I get what's happening - for everything except composite types the schema filter is redundant