docs(faq): add tutorial showing how to re-run a single CI workflow job

[petermetz]

1. This is something that will come in handy as a reference material
   while advising people on how to save on continuous integration
   resources (which are precious)
2. Refactored the table of contents to be auto-generated by the VSCode
   extension "Markdown All-in-One" so this way we don't have to keep it
   up to date manually.
3. Also replaced mentions of "Cactus" with "Cacti" in a couple of the
   older FAQ entries.

Signed-off-by: Peter Somogyvari [email protected]

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[izuru0]

LGTM

[jagpreetsinghsasan]

LGTM

[outSH]

• Please add this new entry to table of contents at the top of this page.
• (optionally) I'd also highlight that the refresh button next to search bar can be used as well

[petermetz]

• Please add this new entry to table of contents at the top of this page.

  • (optionally) I'd also highlight that the refresh button next to search bar can be used as well

@outSH Thank you for the suggestions, I've applied the changes for both of those points!

[outSH]

Great, thank you!