🔧 fix: API Key Handling for GoogleSearch and TavilySearch Tools

[jung0han]

Summary

This pull request addresses several issues and improvements related to handling API keys for GoogleSearch and TavilySearch tools.

• Fixed the way user-provided API keys are handled, ensuring they’re fetched correctly.
• Improved error handling to give clear feedback when environment variables are missing.
• Added new test cases to make sure everything works as expected.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

To test these changes:

1. Run the unit tests for the GoogleSearch and TavilySearch:

npm run test api/app/clients/tools/structured/specs/GoogleSearch.spec.js
npm run test api/app/clients/tools/structured/specs/TavilySearchResults.spec.js

2. Manually test the GoogleSearch and TavilySearch functionality in the application, ensuring that:

• Ensure TAVILY_API_KEY, GOOGLE_SEARCH_API_KEY, and GOOGLE_CSE_ID are not set in the .env file.
• In Assistant Tools, add GoogleSearch and TavilySearch plugins, providing the required API key fields.
• Write and execute a prompt using these tools.
• Verify that an error occurs due to the API keys not being retrieved correctly.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes

[danny-avila]

Thanks! lgtm