Make it clear that git status is introduced in Episode 3 (issue #685)

[jdvorak001]

I am suggesting this fix to issue #685.

[munkm]

Hey @jdvorak001 thanks for the review request! I'm sorry it's taken a bit to get to your PR. I'll do my best to get to it this week!

[jdvorak001]

Thanks for the review. It certainly is not the intent of this path to explain nested repositories, let alone promote them. It just warns against them (as does the currently released version). What I tried to plant is the good practice of running git status before git init. With that, the git status command is introduced a little.

[kekoziar]

I'm going to close this PR in preparation of the new workbench lesson architecture, but with the following points which halted the original merging of this PR.

PRs should be limited to one issue per PR. This PR attempted to do many things, and so the original issue - introducing git status at the very beginning - was lost and never implemented. I happen to tell learners that if they need to remember only one thing, it's git status. I absolutely agree with and approve moving it to prior to git init with explanation. However, there were questions about the other content that was added to the PR. Please submit issues as separate PRs in the future.