Update modeling bug announcement, now that things are working again

Also, while we're here! To restore the lost data, I:

1. Downloaded this scheduled public data backup, which was taken
   thankfully the day before we updated modeling code!
   https://impress.openneo.net/public-data/2024-11-03T08_15_02Z-scheduled.sql.gz
2. Trimmed it just to the section about the `parents_swf_assets` table:
   dropping it, then rebuilding it from scratch.
3. Ran this modified backup SQL dump on the production server.
4. Ran the code from `db/migrate/20241001052510_add_cached_fields_to_items.rb`
   to bring items' cached fields back into the correct state.

I also had to fix some errors in the item data that prevented some
items from passing the latest validations:

```rb
Item.where(rarity: "").update_all(rarity: "???")
Item.where(description: "").update_all(description: "???")
Item.where(zones_restrict: "").update_all(zones_restrict: "00000
00000000000000000000000000000000000000000000000")
```

app/views/outfits/new.html.haml

@@ -11,13 +11,14 @@
     .content
       %p
         %strong
-          Modeling is down, and some items are broken!
+          Oops, sorry for the bugs recently!
         For the first time in One Million Years, we made some changes to our
-        modeling code—and it looks like we goofed it, and some items are losing
+        modeling code—and it looks like we goofed it, and started gradually
-        data!
+        losing some data!
       %p
-        We've turned off modeling while we work to restore a backup, and then
+        We've restored a backup from before we made these changes, so most
-        we'll fix the mistake and turn it back on. Sorry about this!
+        everything is back in order! None of your personal data was affected.
+        Sorry for the disruption, and hope everyone is doing okay! 💜
 
 #outfit-forms
   #pet-preview