chore: migrate to turbo repo to avoid nx issues

[moldy530]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR primarily updates the project by introducing Turborepo for task management, updating dependencies, and enhancing configuration files. It also modifies several components and scripts to improve build processes and project structure.

Detailed summary

• Added turborepo configuration in turbo.json.
• Updated vocs dependency version to ^1.0.0-alpha.62.
• Modified build scripts in package.json to use turbo.
• Adjusted ESLint configurations and ignored files in .eslintignore.
• Enhanced tailwind.config.cjs for content paths.
• Updated README.md with team-specific instructions.
• Changed Sidebar.js logic for active child items.
• Refactored API key handling in smart contract files.
• Updated GitHub workflows to include TURBO_TOKEN and TURBO_TEAM environment variables.
• Removed obsolete patch file and updated .gitignore.

The following files were skipped due to too many changes: yarn.lock, node_modules/vocs/_lib/vite/.vocs/cache/twoslash.json, node_modules/vocs/_lib/vite/.vocs/cache/search.json

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 8:15pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 8:15pm

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “graphite-merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[moldy530]

• chore: migrate to turbo repo to avoid nx issues #1141 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @moldy530 and the rest of your teammates on Graphite

[moldy530]

We will continue to use lerna to publish packages for now. I looked at using auto from intuit, but that library has an issue in repos that have a huge amount of commits at the moment, so will revisit that later.

[moldy530]

looking at the logs for this branch, caching reduced build times for the vercel projects by an order of magnitude