Feature: Define tools in character file

[jfrank-summit]

Description:

To improve flexibility and control over which tools are available in specific workflows, we want to move tool binding from hardcoded definitions to the <your_character>.yaml file. While tool implementations will remain in the codebase, only the tools explicitly listed (by name) in the character file will be bound to workflows. This change allows for better customization and ensures that workflows only have access to the tools they need.

Proposed Changes:

• Add a tools section in the character.yaml file where users can list the names of tools to be bound to workflows.
• Update the framework to dynamically bind only the tools listed in the character.yaml file to workflows at runtime.