fix(docs): remove component page hash replacement

[GreenTeaCake]

Closes #3527 and affects #2732 (removes componentWillMount from ComponentDoc).

[welcome]

💖 Thanks for opening this pull request! 💖

Here is a list of things that will help get it across the finish line:

• Run yarn lint locally to catch formatting errors. This will fix some errors automatically, commit and push any changes.
• Run yarn test locally to catch errors. This ensures all components still behave as they should.
• Run yarn start to run the doc site locally and try a few pages, ensuring everything is in good working order.
• Include tests when adding/changing behavior.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[codecov-io]

Codecov Report

Merging #3528 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3528   +/-   ##
=======================================
  Coverage   99.82%   99.82%           
=======================================
  Files         172      172           
  Lines        2795     2795           
=======================================
  Hits         2790     2790           
  Misses          5        5

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3db04da...60074ca. Read the comment docs.

[layershifter]

@grumblerchester thanks for pushing this. It's weird, I removed this part of code and it still works 🦀 Can you please confirm?

[GreenTeaCake]

@layershifter Yeah! Deletion resolves the issue too and everything works absolutely fine for old hashes.
But I'm not sure what "hash replacement for new hashes" is supposed to do. 🤢

[layershifter]

Can you please clarify what is "old" and "new" hashes?

[GreenTeaCake]

@layershifter Please see isOldHash that is used by getFormattedHash.
I have an assumption that these terms were introduced during some migration but not sure if the migration is completed.

[layershifter]

I see, yep it was introduced in #2760 to fix #2737.

Actually, it was year ago and I don't see there a big issue that some of extra old links can be broken as they will still point to the correct page.