Split CI and publish runs into separate workflows

[rnestler]

The workflow got completely stopped, since it contains scheduled triggers and there was no activity on the repository for months. By splitting that, we avoid the CI workflow from breaking.

[rnestler]

I think the issue was something different: The periodic workflow was shown as stopped in https://github.com/SpaceApi/website/actions/workflows/ci.yml since there was no activity on the repository for 3 months. Can we just remove the scheduled run? I'm not sure what the point of it should be.

Or maybe split the ci and publish workflows and only schedule the publish workflow.

[dbrgn]

Oof, that's the issue... Yeah, I usually click on those links in the nag e-mails, but probably forgot it once.

The idea of the scheduled workflow was that containers are re-built regularly (security updates). Not sure how important that is for a static website.

[dbrgn]

Looks good to me, thanks!

The branch name might still be useful if we want to publish separate branches as separate images, but I guess master is sufficient for now.

Note: I'm fairly sure that the first commit is wrong (the branches key is not required AFAIK), but it doesn't hurt to specify it (assuming that it's referring to the PR target).

[rnestler]

Note: I'm fairly sure that the first commit is wrong (the branches key is not required AFAIK), but it doesn't hurt to specify it (assuming that it's referring to the PR target).

Yeah I noticed this as well and reverted the change when splitting the workflows.