Bug/UX problem: error 404 shows when "Public pipelines" is disabled

When "Public pipelines" option is disabled at GRP/PRJ/settings/ci_cd, a non-member visitor will see all pipelines at GRP/PRJ/pipelines but trying to access a build output will result in an ugly 404 error. User won't have a clue why this happens. To any visitor, it'd be a bug.

See it yourself:

1. Go here: https://gitlab.com/virtkick/chef-server-with-letsencrypt/-/jobs/44252005
2. Click "kitchen" job (which points to https://gitlab.com/virtkick/chef-server-with-letsencrypt/-/jobs/44252005)

I think the remedy is not only to disable a link but also - at the very minimum - to inform a user why they can't access the job.

And the best approach would be to render the build screen but not display the job output and show a generic "Project owner disabled public access to build output." instead. And a link to artifacts, if present, shouldn't be showed. I think this is a very natural and UX-friendly way of solving this issue.