feature/composio

[conneroisu]

• added e2b emulating test server and unit test for sandbox
• added toolhouse test server method on the test server
• remove default logger from test server
• run tidy on go.mod and go.sum in generate-models
• remove generate e2b kernels
• model out more of the interface and remove unused struct for subscribe params
• save local testing progress
• added start to exmaple of e2b module
• added start of composio extension
• made a composio example for better development
• added request builders to composio
• added composio client comment to new composio client
• change to subscribestdout and subscribestderr and subscribeexit
• Added get tools params
• update go version
• make toolhouse execution more efficient and implement composio execution
• moved tools to pkg/tools
• added retru log to sandbox.read
• broke out the tet servers into their own files for each service
• working composion extension
• optimize readability in composio and make sure e2b is concurrent safe
• added composio test server function
• added unit test which is triggered by a workflow dispatch
• update go versions in workflows
• finished composio inferface
• removed unit test in composio
• added auther interface to composio client and cleaned up getconnectedaccounts
• rename unit test inside auth_test
• adjust to new connected account response/struct
• add with base url to options for composio
• add label to options for e2b
• remove uneeffectual ctx declaration in unit test
• clean up the error message return for the tooling wrapper
• more readable tools in e2b.tools
• added encoding functions to test package
• finish this composio integration

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14251772	Triggered	Generic High Entropy Secret	353e6f3	extensions/composio/test.sh	View secret
14251772	Triggered	Generic High Entropy Secret	22bda71	extensions/composio/test.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}