Update Exa Search tool to current API

[10ishq]

Updates the Exa Search node to current API conventions:

• Search types updated to auto, fast, instant, deep (removed keyword/neural)
• Categories limited to the current 6
• Added maxAgeHours parameter
• Removed useAutoprompt from UI
• Added x-exa-integration: flowise-integration header

[gemini-code-assist]

Code Review

This pull request updates the ExaSearch tool by adding new search types and a maxAgeHours parameter, while removing the useAutoprompt option and refining categories. Feedback indicates that the integration header implementation may be non-functional due to SDK limitations. Additionally, suggestions were made to improve type safety for search parameters and to trim whitespace when parsing domain lists.

[gemini-code-assist]

The Exa client from the exa-js library does not typically expose or utilize a headers property on the instance for its requests. The internal request method in the SDK usually constructs headers dynamically using only the apiKey. Consequently, setting (client as any).headers is likely non-functional, and the x-exa-integration header will not be sent to the API.

If the SDK version used does not support custom headers in the constructor or via a public property, this integration tracking might not be achievable through the SDK instance directly. You should verify if the header is actually being sent in your tests.

[gemini-code-assist]

The type for type has been generalized to string | undefined, which reduces type safety. Since the supported search types are now a fixed set, it is better to use a union of the allowed string literals to maintain compile-time validation.

Suggested change

	const type = nodeData.inputs?.type as string | undefined
	const type = nodeData.inputs?.type as 'auto' | 'fast' | 'instant' | 'deep' | undefined

[gemini-code-assist]

When splitting domains by comma, users might include spaces (e.g., "example.com, test.com"). It is recommended to trim each domain string to ensure the API receives clean values without leading or trailing whitespace. This approach of using simple, chained operations improves readability and reduces potential errors.

Suggested change

	includeDomains: includeDomains ? includeDomains.split(',') : undefined,
	excludeDomains: excludeDomains ? excludeDomains.split(',') : undefined,
	includeDomains: includeDomains ? includeDomains.split(',').map((d) => d.trim()) : undefined,
	excludeDomains: excludeDomains ? excludeDomains.split(',').map((d) => d.trim()) : undefined,

References

1. Prioritize code readability and understandability over conciseness. A series of simple, chained operations can be preferable to a single, more complex one if it improves understandability and reduces the potential for future errors.