Pipeline order changes if there is a 'pages' job in the middle of the list

Summary

If you've a pipeline with a pages job that is not in the last stage, when the pages:deploy job is automatically created the stage is moved to the end of the pipeline.

Steps to reproduce

Create a pipeline with pages in a middle stage.

Example Project

https://gitlab.com/bikebilly/demo-dep/pipelines/9588913

What is the current bug behavior?

The Deploy stage is the last stage in the list

What is the expected correct behavior?

The Deploy stage is between Doc and Trigger