Fix permissions check for destroy epic-issue link

What does this MR do?

It fixes the permission check if a user can destroy epic-issue association.

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

Why was this MR needed?

We checked admin_issue_link instead of admin_epic_link

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan

What are the relevant issue numbers?

Closes #4044 (closed)