Revise subheading to bring it up to date

What does this MR do?

Updates https://docs.gitlab.com/ee/user/project/merge_requests/changes.html#ignore-whitespace-changes-in-merge-request-diff-view to provide full instructions, and replace the outdated screenshot with a current one (complete with version number).

Kai's other request (to add the introduced-in line) I can't fulfill - it's well outside of the supported versions, which we've been removing: https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#removing-versions-after-each-major-release

Related issues

Closes #334323 (closed)

Author's checklist

• Follow the Documentation Guidelines and Style Guide.
• Ensure that the product tier badge is added to doc's h1.
• Request a review based on the documentation page's metadata and associated Technical Writer.

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

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.