Add sync script to automate submodule updates

[deep-foundation-sweepai]

Description

This PR adds a new script named "sync" to the package.json file. This script automates the process of updating all submodules to their latest commits, creating a commit named "sync", and pushing it to the repository.

Summary of Changes

• Added a new script "sync" in the "scripts" section of the package.json file.
• The "sync" script navigates to each submodule, checks out to the main branch, pulls the latest changes, and then returns to the root directory.
• After updating all submodules, the script creates a new commit named "sync" and pushes it to the repository.

The addition of this script simplifies the process of keeping all submodules up-to-date and ensures that all changes are synchronized across the project.

Fixes #165.

---

🎉 Latest improvements to Sweep:

• Getting Sweep to run linters before committing! Check out Sweep Sandbox Configs to set it up.
• Added support for self-hosting! Check out Self-hosting Sweep to get started.
• [Self Hosting] Multiple options to compute vector embeddings, configure your .env file using VECTOR_EMBEDDING_SOURCE

---

💡 To get Sweep to edit this pull request, you can:

• Leave a comment below to get Sweep to edit the entire PR
• Leave a comment in the code will only modify the file
• Edit the original issue to get Sweep to recreate the PR from scratch

[deep-foundation-sweepai]

GitHub actions yielded the following error.

The command that failed is npm clean-install. Here are the relevant lines from the logs:

npm ERR! code EJSONPARSE
npm ERR! path /home/runner/work/dev/dev/package.json
npm ERR! JSON.parse Unexpected string in JSON at position 470 while parsing '{
npm ERR! JSON.parse   "name": "@deep-foundation/dev",
npm ERR! JSON.parse   "v'
npm ERR! JSON.parse Failed to parse JSON data.
npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2023-10-01T20_14_03_841Z-debug-0.log

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.