Make pages job run in separate schedule

Currently, the pages deployment is part of the complexity measurement pipeline.

There is a some-call-it-bug-some-call-it-feature with the special gitlab pages pages:deploy job that makes it fail if the build SHA is not the most recent one on the current branch anymore. In other words: if someone merges to main after the complexity measurement pipeline has finished, the page deployment will fail. That is rather likely to happen as the whole pipeline can take about 15 hours to finish completely.

The logical workaround to me is to make the pages job run on a separate schedule maybe 4 times a day to only update the page. Since fetching of the artifacts is happening via the api anyway, this should not be a problem and also not create any big extra load on the runners as the job only downloads the artifacts, unzips them and copies things around. The most recent runs took <20s.