Remove detailed fork/clone instructions

[josh-works]

As mentioned in turingschool/mod-0-curriculum#30, and per @damwhit and I's conversation, it would be reasonable to copy the fork/clone instructions from the backend capstone repo to the mod0 repo.

On https://github.com/turingschool-examples/module_0_capstone, there are some instructions/screenshots about how to fork/clone the back-end repository, specifically here.

The screenshots have useful information in them, but it adds to the maintenance burden of maintaining the mod0 repo, and capstone repositories for the front-end AND back-end programs, if we have duplicate information across all three.

I'd love to remove the fork/clone instructions out of the back-end capstone README, and bring them to the mod0 section on fork/cloning a repositry: http://mod0.turing.io/session4/#forking

(Maybe as they're removed, give a link to the instructions in the mod0 curriculum)

[damwhit]

@josh-works love this! Keeping one source of truth (and one place to maintain) is ideal in my opinion. Just a heads up, I'll be moving some things around in the curriculum, where sessions 2 - 5 will be moved up and become 1 - 4 and we'll be adding a new session.

[damwhit]

@josh-works I converted the frontend capstone to be more inline with backend one from a structural perspective - Now it's a repo instead of just instructions on the mod0 site. In doing so I copied the following over from the backend:

• the main readme forking instructions
• day 0
• the submission instructions in day7

[damwhit]

I'm wondering if it would be best to have the forking instructions and submission instructions as partials in the _includes directory that we can link to in each capstone page on the mod 0 site.