feat(site-builder): add new package to config, expose destroy command

[giac-mysten]

Closes SEINT-357
Closes SEINT-371

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
walrus-sites-sp	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2024 10:44am
walrus-sites-sp-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2024 10:44am
walrus-sites-sw	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2024 10:44am
walrus-sites-sw-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2024 10:44am

[codspeed-hq]

CodSpeed Performance Report

Merging #318 will not alter performance

_{Comparing gg/site-builder/update-package-and-burn (75c182f) with main (4d1e19e)}

Summary

✅ 3 untouched benchmarks

[Tzal3x]

Sweet! Thank you 🙇‍♂️ Some newborn questions:

1. This only deletes already "expired" sites right? Sites that the blob of the resources have been gone past their epoch expiration, so they are deleted. And the user just wants to take the reimbursement by deleting the no-longer needed sui objects.
2. If a user needs to delete a site, before that expiring, this functionality is not supported yet in the site-builder right? Meaning that during publishing he should define the resource blobs as deleteable, delete them, and then have a separate function (maybe different than destroy?) that deletes the blobs first, and then calling site-builder destroy?

[giac-mysten]

1. This only deletes already "expired" sites right? Sites that the blob of the resources have been gone past their epoch expiration, so they are deleted. And the user just wants to take the reimbursement by deleting the no-longer needed sui objects.

2. If a user needs to delete a site, before that expiring, this functionality is not supported yet in the `site-builder` right? Meaning that during publishing he should define the resource blobs as deleteable, delete them, and then have a separate function (maybe different than destroy?) that deletes the blobs first, and then calling `site-builder destroy`?

Ah this is actually an excellent point. Currently, the destroy command does not touch the blobs on walrus. Only removes the Site object and dynamic fields from Sui. Which may not be what people want. However, we do not support deletable sites at the moment. So a bit more thinking may be actually needed here to decide what is best to do.

Possibly a good idea would be to always publish sites as deletable blobs, unless someone explicitly adds the --permanent flag.

[Tzal3x]

Ok, let's merge this and we then can proceed by building the deletable blobs functionality in a following PR.