fix: hubble autoupgrade should ensure dependencies and clean unused docker data

[sanjayprabhu]

Motivation

Fixes #1528. And also docker volumes taking up too much space.

Change Summary

Describe the changes being made in 1-2 concise sentences.

Merge Checklist

Choose all relevant options below by adding an x now or at any time before submitting for review

• PR title adheres to the conventional commits standard
• PR has a changeset
• PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
• PR includes documentation if necessary.
• All commits have been signed

Additional Context

If this is a relatively large or complex change, provide more details here that will help reviewers

---

PR-Codex overview

This PR focuses on fixing the hubble autoupgrade process by ensuring dependencies and cleaning unused docker data.

Detailed summary

• Patched the "@farcaster/hubble" package.
• Updated the restart policy in the hubble/docker-compose.yml file.
• Added a check to skip self upgrade for easier testing.
• Added a cleanup function to prune unused docker images and volumes.
• Installed dependencies and docker as root in the autoupgrade script.
• Added a sleep command before cleanup in the autoupgrade script.

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

[changeset-bot]

🦋 Changeset detected

Latest commit: 04cb193

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@farcaster/hubble	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
hub-monorepo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 20, 2023 7:52pm

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 3 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[mscurtescu]

Why was the restart policy changed from unless-stopped to on-failure?

Adding max 5 restarts makes sense, is this not available for unless-stopped?

With on-failure there is the problem that the container will not start after a host machine reboot, for example. The service is less resilient this way.