Updating Turbo commands to fix build edge cases

I was able to simplify our Turbo commands and fix the pnpm dev command by manually upping the concurrency limit. My machine would never boot up the Next JS servers due all of the watch commands never resolving (by design). I did a bunch of testing with other values like 100%, but that still didn't work on my machine - so I finally just settled on passing a fixed number of 30 for max concurrent scripts.

https://turbo.build/repo/docs/reference/command-line-reference/run#--concurrency

I did a bunch of testing on my machine and it seems like these changes certainly help fix a few issues. The wallet-selector-control package still likes to spit out a TypeScript error during the build step, but the package still builds and resolves correctly.

It appears that Turbo has issues correctly resolving the dependency graph when relying on peerDependencies. I attempted to update our packages to reference each other as dependencies, but then that totally broke everything due to shenanigans from @near-js/providers (which our Social DB package depends on).

Besides the annoying TS error, I believe everything is in a working state now to unblock us.

Name	Status	Preview	Updated (UTC)
bos-web-engine	✅ Ready (Inspect)	Visit Preview	Apr 23, 2024 10:02pm
bos-web-engine-docs	✅ Ready (Inspect)	Visit Preview	Apr 23, 2024 10:02pm
bos-web-engine-sandbox	✅ Ready (Inspect)	Visit Preview	Apr 23, 2024 10:02pm

near / react-on-chain

Updating Turbo commands to fix build edge cases #426