[CI-4292] Automate Table of Contents Generation using Doctoc

[Mudaafi]

PR Description

1. Adds doctoc as a dependency
2. Creates a pre_push post_commit script using husky to seamlessly run doctoc if the README.md file has been updated, ensuring that the TOC always remains updated. (This could be a GHA as well)

[Mudaafi]

This will automatically amend the commit that is about to be pushed to remote. It's seamless, so as a contributor you might not even realize your final commit has been changed before it was pushed. That said, it lowkey scares me so we could make it a manual process instead.

[Mudaafi]

Update: @esezen suggested maybe adding a new commit instead of amending the existing one, but it turns out that doesn't play well cc: https://stackoverflow.com/questions/21334493/git-commit-in-pre-push-hook

[esezen]

@Mudaafi let me know if this is a problem on my end but the pre-push hook is pushing the original commit rather than the amended one for me. So instead of doing amend and push, it does push and amend which creates a divergent branch (?) between origin and local 🤔

My local has the updated ToC but the version that gets pushed to GH doesn't

[Mudaafi]

@esezen Hmm it works for me. Let's hop on a sync

[Mudaafi]

@enes @mocca102 Following our discussion, since amending the commits in-flight when a git push is run leads to flaky behavior, I've modified the script to be a post_commit hook instead. Logic is similar, but now it adds a new, separate commit if the README.md changes result in a TOC update.

[esezen]

LGTM!