Run Celeste TASes on pull requests

[maddie480]

Tested on this PR: #915 because it needed to target a branch that actually had the GitHub Actions yaml in order to run it.

The action:

• Waits for the build to be completed on Azure, polling every minute, filtering on the commit SHA
• Pulls the everest:vanilla Docker image, which is just Ubuntu with a bare-bones Celeste in it, and no Everest (despite the name). We can't pull an encrypted Celeste and decode it with a secret, because pull request pipelines don't have access to secrets, so here we go
• Downloads the build artifact from Azure and installs Everest from it
• Downloads CelesteTAS, the TAS files and the Strawberry Jam bundle ™️ from Banana Mirror (they're static, so a mod update breaking TASes won't break the build)
• Runs Celeste with special command line parameters that tell CelesteTAS to run the TAS, write the report and close the game
• Checks if the report says "success"

[maddie480]

This new shiny pipeline epicly failed because of an unrelated crash fixed in #913. 😅

[Wartori54]

I think that fetching the tas files from the repo, and checking out a hard coded commit could be better. Same thing with the CelesteTAS version, if it can be fetched from gb or GitHub releases.
That would be good for transparency, and also adds the ability for people without celestemodupdater access to bump and inspect versions more easily.

For the required mods for each run (such as the SJ bundle), I can't think of a better alternative, so it's probably fine as is.

[maddie480]

fixed, only the pinned SJ bundle remains on celestemodupdater

[psyGamer]

Seems reasonable and should cover most obvious issues early. CelesteTAS also provides a utility program for simply executing the sync-check from a config file tho I suppose the features it provides aren't really useful to Everest (optionally installing latest version of an Everest branch, updating mods, better handling for running multiple TAS files, calculating a checksum to avoid repeated work) and therefore makes sense to use a custom script. For CelesteTAS a full sync-check is required before releasing (which takes 20min and therefore caching a nightly check is useful), but since Everest has structured it a bit differently, it seems reasonable.

Alright, enough rambling lmao

[maddie480-bot]

The pull request was approved and entered the 3-day last-call window.
If no further reviews happen, it will end on Jun 15, 2025, 12:00 AM UTC, after which the pull request will be able to be merged.