docs: creating a redirect for a legacy link about pre-commit hook

[rusackas]

SUMMARY

I google for the pre-commit hook docs all the time, and Google thinks it's a dead-end. Hopefully this fixes it.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[sfirke]

When should one redirect via the .htaccess file vs. in Docusaurus? Compare this to my PR here: #28496

It looks like this way supports linking to a subheading link, which had my pending PR failing CI, so maybe this is better?

[rusackas]

I'm actually not sure... as it stands, this PR did not actually work.

https://superset.apache.org/docs/contributing/hooks-and-linting/
^^ the link here is a dead-end, as of this writing

I'm also not sure if a frontend redirect eventually teaches the googlebots where to point. One would think so.