Use GitLab Pages v0.4.1

What does this MR do?

Switches to GitLab Pages v0.4.1, fixing a long-standing bug for projects with multiple custom domains

Are there points in the code the reviewer needs to double check?

The only change in Pages is https://gitlab.com/gitlab-org/gitlab-pages/merge_requests/27

Why was this MR needed?

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Tests
  • All builds are passing
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-pages/merge_requests/27 https://gitlab.com/gitlab-org/gitlab-pages/merge_requests/26 https://gitlab.com/gitlab-com/support-forum/issues/1740

@ayufan @jpap I think it makes sense for this to be in 9.1. I don't know if we should backport it to 9.0 or not

This feature seems to have been broken for at least a year, possibly longer.

mentioned in issue gitlab-com/support-forum#1740 (closed)

added 43 commits

• 0723cdfc...04811cbb - 42 commits from branch gitlab-org:master
• 7b3d6b25 - Use GitLab Pages v0.4.1

Compare with previous version

approved this merge request

merged

mentioned in commit afaa99f4

Picked into 9-1-stable, will go into 9.1.2

mentioned in commit 7f9fe93d