Define user permissions to view and create related epics

Related to #202431 (closed)

Any epic can be related/blocked by another (despite the group they belong to). The ability to see and relate the epics will be determined at the user level. IOW, the linking ability depends on the user permissions and not the relationship of the resources.

For related issues, we use the following permissions

• admin_issue_link to determine if the user can relate the issues

Requirements

1. New GitLab Ultimate license (e.g related_epics) similar to existing subepics)
2. Check that the user is at least a reporter in the target epic's group to set epics as related. We already have admin_epic_link that requires reporter+ plus subepics_available, so we probably need a new policy. See #351597 (comment 838361958) for more details.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.