Pull in Launchpad components

[runleveldev]

mieweb/launchpad currently is a fully seperate project and is easy to forget about when making API changes. We want to keep the mieweb/launchpad branding but move the core components here. To accomplish this, we should implement smaller individual actions in this repo under .github/actions. We should at least subdivide it into create-container.yml and delete-container.yml. Launchpad would then consume these as uses: mieweb/opensource-server/.github/actions/create-container.yml@latest. Any part of launchpad the consumes the API should be wrapper here and only launchpad-specific logic should remain in its own repo.

[runleveldev]

Taking a look at launchpad we'll probably need the following actions here:

Target Filename	Purpose	Used in launchpad step	API Route
.github/actions/get-container.yaml	Fetch container information by hostname	manage-container, container-status	GET /api/v1/sites/$SITE_ID/containers?hostname=$CONTAINER_NAME
.github/actions/delete-container.yaml	Delete a specific container by id	manage-container, Container Deletion on Branch Deletion	DELETE /api/v1/sites/$SITE_ID/containers/$CONTAINER_ID
.github/actions/create-container.yaml	Create a container with parameters	manage-container	POST /api/v1/sites/$SITE_ID/containers
.github/actions/wait-for-job.yaml	Poll a job until completion by id	wait-job	GET /api/v1/jobs/$JOB_ID

wait-for-job.yaml could be a step in create-container.yaml but there may be motivation to reuse wait-for-job in future if steps to modify existing containers are needed.

[runleveldev]

One other thing this will do is allow pinning versions. So when I tag the v2026.6.2 release if there's breaking API changes any you need to use a cluster that isn't there yet you can pin your action to v2026.6.1. The only way that works though if there's an easy way to pass through the release through launchpad. I.e., I use: mieweb/launchpad@v2026.6.1 and that then calls to use: mieweb/opensource-server/.github/actions/create-container.yaml@v2026.6.1. Hopefully there's a magic variable like ${action.ref} that passes the @<whatever> through, but more likely we'd have to tag specific mieweb/launchpad releases to match opensource-server releases. We can consider that a stretch goal for now seeing as we only have one cluster.

[runleveldev]

Completed in #367