feat: expose searchDomainFilter and searchRecencyFilter in Perplexity…

[PythonToGo]

Problem

The Perplexity node had searchDomainFilter and searchRecencyFilter UI fields commented out, making them inaccessible to users despite being fully supported by both the LangChain wrapper and the Perplexity API.

The init() function already reads and passes these fields to the model — only the UI definitions were missing.

Changes

Uncommented the two UI input fields in ChatPerplexity.ts:

• Search Domain Filter (searchDomainFilter): Allows users to restrict citations to specific domains (e.g., ["example.com", "docs.mycompany.com"])
• Search Recency Filter (searchRecencyFilter): Allows users to filter search results by time interval — hour, day, week, or month

returnImages and returnRelatedQuestions remain disabled as their output is stored in additional_kwargs and not yet handled by Flowise's response pipeline.

Why no backend changes

The LangChain PerplexityChatInput interface already declares both fields, and invocationParams() already maps them to the Perplexity API (search_domain_filter, search_recency_filter). The init() function in Flowise also already reads and passes them. This PR only restores the UI exposure.

[gemini-code-assist]

Code Review

This pull request uncomments and enables the 'Search Domain Filter' and 'Search Recency Filter' configuration options for the ChatPerplexity component. A review comment suggests improving the user experience for the domain filter by using a string list type instead of a raw JSON field.

[PythonToGo]

Regarding the Gemini suggestion to use type: 'string' with list: true —
I kept type: 'json' because this combination doesn't appear anywhere in the
existing chatmodel nodes, and the init() logic was written specifically for
JSON input. Happy to change it if you prefer a different approach.