filterSchemas property does not work on singer tap PipelinewisePostgres

[Slasher154]

Expected Behavior

When filterSchemas property of tap PipelinewisePostgres plugin is configured, the discovery should scan only the schemas provided.

Actual Behaviour

The tap still scan all schemas despite providing the filterSchemas property.

Steps To Reproduce

1. Config the plugin singer tap PipelinewisePostgres with filterSchemas property and stream configuration with table that does not exist in that schema but other schema in the same db.
2. Run the flow. It should not find the table since the table does not exist in the provided schema list. But the tap is able to extract that table.

Environment Information

• Kestra Version: 0.18.0
• Plugin version:
• Operating System (OS / Docker / Kubernetes): Docker
• Java Version (If not docker):

Example flow

No response