Update git instructions to follow redirects

What does this MR do?

The URI provided for Git 2.18.0 is returning a 301. This causes the existing download instructions for Git curl --remote-name --progress https://www.kernel.org/pub/software/scm/git/git-2.18.0.tar.gz to pull down a redirect page instead of the expected archive. This MR updates the Curl command to follow the redirect.

Updated command: curl --remote-name --location --progress https://www.kernel.org/pub/software/scm/git/git-2.18.0.tar.gz

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

Why was this MR needed?

Current instructions do not work

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
• Conforms to the code review guidelines
  • Has been reviewed by a UX Designer
  • Has been reviewed by a Frontend maintainer
  • Has been reviewed by a Backend maintainer
  • Has been reviewed by a Database specialist
• EE specific content should be in the top level /ee folder
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• If you have multiple commits, please combine them into a few logically organized commits by squashing them
• 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
• End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?