Revise very wordy expiry messages

What does this MR do?

@pedroms asked me to review all the UI messages related to merge requests. When I grepped for strings, I found the ones I expected, plus messages in other areas that made references to merge requests. (Full spreadsheet here.)

This MR revises these three messages to fix grammar and remove wordiness:

• Message 1:
  • After that it expires, you will not be able to can't use merge approvals, or code quality, or as well as many other features.
• Message 2:
  • After that it expires, you will not be able to can't use merge approvals, or epics, or as well as many other features.
• Message 3:
  • After that it expires, you will not be able to can't use merge approvals, or epics, or as well as many security features.

Related issues

• Related to #346051 (closed) for the merge request UI messages we cleaned up in %14.5.

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.