No indication of why project visibility setting is disabled when forked from private project
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=26875)
</details>
<!--IssueSummary end-->
When a project is forked from a private project, the expected behaviour is that the visibility setting cannot be changed from `private`. However, there's no indication of any reason why it is disabled which can lead to confusion for users not familiar with this feature. It was already reported incorrectly as a bug: https://gitlab.com/gitlab-org/gitlab-ce/issues/40088
Can we add a note or improve gitlab-ce~2024184 somehow?
issue