Refactor directory structure

[akihikokuroda]

Which issue(s) does this pull-request address?

#14 This is the first proposal.

Closes: #14

Description

Restructure directories to contain most of changes in one tool under one directory

Checklist

• I have read the contributor guide
• Linting passes: yarn lint or yarn lint:fix
• Formatting is applied: yarn format or yarn format:fix
• Unit tests pass: yarn test:unit
• E2E tests pass: yarn test:e2e
• Tests are included
• Documentation is changed or added
• Commit messages and PR title follow conventional commits

[grahamwhiteuk]

@akihikokuroda is this still WIP?

[akihikokuroda]

It's ready for review and comments. I'll take out WIP, Thanks!

[grahamwhiteuk]

Great, thanks. Could you rebase to main? I've just updated the core dependencies across the project.

[grahamwhiteuk]

Thanks. Could you also go through the PR check list and tick off the items you're able to.

[akihikokuroda]

E2e tests work except tests that require API key.

[grahamwhiteuk]

No probs, I'll check those out as part of my review - many thanks for your contribution!

[grahamwhiteuk]

This PR looks a bit muddled to me as it stands right now. I would recommend the following changes:

Re-instate Global Examples
The examples are intended to show the creation of agents using the tools. Some examples may be specific to an individual tool such as that for Airtable where specific information is required to configure it. Some other examples are generic across multiple tools such as that for ImageDescription and OpenLibrary. This move also makes it unclear what would be run from the default "start" command in package.json.

Re-instate a default agent
Setting the start script to tsx is not what I would expect as a user. The default start script should run an example agent that requires no further configuration from the user.

Don't exclude tests
All tests should be run. Some tests have been excluded in package.json

Locate all tests under the tests subdir
It's confusing to have only e2e tests located under the tests subdir and not the unit tests

Dont use @ imports
There is a specific tsconfig set up such that imports can be namespaced as bee-community-tools similar to the way the library would be used in the wild.

[akihikokuroda]

@grahamwhiteuk Thanks for review. I believe that all comments have been addressed.