Remove Issue Data and Actions docs page

What does this MR do?

https://docs.gitlab.com/ee/user/project/issues/issue_data_and_actions.html is out of date and needs to be deleted.

1. Identify parts of it that are not documented anywhere else and move them elsewhere:
   • Reference - make into a task topic and add to https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/project/issues/managing_issues.md
   • Email - make into a task topic and add to https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/project/issues/managing_issues.md
   • Mentions - move to https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/discussions/index.md
   • Award emoji is covered in https://docs.gitlab.com/ee/user/award_emojis.html. Remove.
   • Create merge request - mention in https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/project/merge_requests/getting_started.md#user-content-merge-requests-to-close-issues
   • Activity sort order move to https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/discussions/index.md
   • Publish an issue move to https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/project/issues/managing_issues.md
2. Delete the issue_data_and_actions.md page and also:
   • Set a redirect to https://docs.gitlab.com/ee/user/project/issues/
   • Delete images in https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/project/issues/img that are only linked from the Data and Actions page.
3. 🎉 🥂

Related

• #294506 (closed)
• gitlab-com/www-gitlab-com!94464 (merged) - MR to fix links in www-gitlab-com
• gitlab-docs!2283 (merged) - remove page from docs nav

Author's checklist

• Consider taking the GitLab Technical Writing Fundamentals course
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• Ensure that the product tier badge is added to topic's h1.
• Request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are only adding documentation, do not add any of the following labels:

• ~"type::feature"
• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
• Ensure a release milestone is set.