openrct2: 0.4.31 -> 0.4.32, add update script

[keenanweaver]

• Bumped to latest tag 0.4.32
• Renamed openmsx as that has now changed
• Added an update script now that the assets are loaded from an external JSON. We can now use r-ryantm for updates! See: OpenRCT2/OpenRCT2@37545df
• Removed the check and notes regarding that since it's no longer relevant

I am not in love with the update script. Any suggestions for elegance are greatly appreciated. I will change it for the next release to look at the previous tag's assets.json--might be able to clean up a lot. I used other update.sh's in the tree, but I'm really unsure what is a 'best practice' setup for a custom update script.

Changelog: https://github.com/OpenRCT2/OpenRCT2/releases/tag/v0.4.32
Diff: OpenRCT2/OpenRCT2@v0.4.31...v0.4.32

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

[keenanweaver]

nixpkgs-review result

Generated using nixpkgs-review-gha

Command: nixpkgs-review pr 495854
Commit: 64db2497e41c788dacb117c555ad30ce04b319ed (subsequent changes)
Merge: 19b430395e6ff16a4f8d11bd6c203a0cf1429b3b

Logs: https://github.com/keenanweaver/nixpkgs-review-gha/actions/runs/22580421584

---

x86_64-linux

✅ 1 package built:

• openrct2

---

aarch64-linux

✅ 1 package built:

• openrct2