docs: split up getting started guide into multiple pages

[Dhaiwat10]

Closes #2086

[Dhaiwat10]

@arboleya I saw you mentioned a 'troubleshooting' page in the original issue. What would you want on this page? Do you have any rough idea/expectations?

[arboleya]

Important

Brainstorming.

@Dhaiwat10 At first, I thought about having a fuels troubleshoot command that could:

1. check for version mismatches
2. check ts settings (example)
3. what else?

Like a utility, it could grow with time, incorporating handy validations and gotchas—think of a brew doctor. Maybe it's overkill, but maybe not. Anyway, in this rationale, the troubleshoot doc page could be a guide about using the new command (which requires implementing the command) or simply a guide to the manual procedures one could use to double-check one's setup.

What do you think?

[Dhaiwat10]

@arboleya I have filed an issue for the troubleshoot command. I think we should just implement it and add the docs along with it when we do it, rather than doing the docs twice.

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
79.54%(+0%)	69.84%(+0%)	77.12%(+0%)	79.65%(+0%)

Changed Files:

Coverage values did not change👌.