Remove Hashed Storage References within documentation

Summary

As Hashed Storage has become the only way to manage GitLab repositories (as far as I know), does it make sense to start purging "references" in ancillary locations about Hashed Storage requirements - like in Design Management? Currently, coming across "hashed storage" references makes one assume that there are other ways. Moreover, it might be helpful to have some documentation that outlines the history of how Git repositories have been indexed.

https://docs.gitlab.com/search/?q=%22hashed%20storage%22&page=1

Implementation Guide

Go through docs and remove mentions of historical references of Hashed Storage or its alternatives.

Hi community contributors! 👋

Do you want to work on this issue?

• If the issue is unassigned, in a comment, type @docs-hackathon I would like to work on this issue and a writer will assign it to you.

  To be fair to others, do not ask for more than three issues at a time.

• If the issue is assigned to someone already, choose another issue. Do not open a merge request for this issue if you are not assigned.

To resolve the issue

Follow these instructions to create a merge request.

• Don't submit your merge request until after the Hackathon has started.
• Try to address the issue in a single merge request.
• Try to stick to the scope of the issue. If you see other improvements that can be made in the file, open a separate merge request.
• When you create the merge request, select the Documentation merge request description template.
• In the merge request's description, add a link to this issue.
• Follow the commit message guidelines. Use three to five words for your commit message, start with message with a capital letter, and do not end it in a period. Other commit messages can cause the pipeline to fail.

Thank you again for contributing to the GitLab documentation! 🎉

Documentation issue