fix: validation for tool name

[edwinjosechittilappilly]

Tool name validation based on open ai Schema for tool names

Note: In case of Agent as Tool. This doesnt work if it tool is a Tool for Agent as tool. Only check when the agent as tool is invoked.
This pull request introduces changes to the agent validation and creation process in the src/backend/base/langflow/base/agents/agent.py file. The most important changes include the addition of a tool name validation method and its integration into the agent-building process.

Agent Validation and Creation Improvements:

• src/backend/base/langflow/base/agents/agent.py: Added a new method validate_tool_names to ensure tool names match a specific pattern using regular expressions. This method checks that tool names contain only letters, numbers, underscores, and dashes, and do not contain spaces.
• src/backend/base/langflow/base/agents/agent.py: Integrated the validate_tool_names method into the build_agent method of the LCToolsAgentComponent class to validate tool names during agent construction.
• src/backend/base/langflow/components/langchain_utilities/tool_calling.py: Added a call to validate_tool_names in the create_agent_runnable method to ensure tool names are validated before creating the tool-calling agent.

Miscellaneous:

• src/backend/base/langflow/base/agents/agent.py: Imported the re module to support regular expression operations for tool name validation.

[phact]

I tested it locally and it works great, I see the error clearly in the UI:

[codspeed-hq]

CodSpeed Performance Report

Merging #4790 will degrade performances by 20.69%

_{Comparing fix-agent-tool-naming (23fbf6c) with main (08849b6)}

Summary

❌ 1 regressions
✅ 14 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	fix-agent-tool-naming	Change
❌	test_successful_run_with_output_type_any	232.3 ms	292.9 ms	-20.69%