Move design types into separate GitHub repositories

[grumpyinca]

Evaluate & confirm that having design types deployed in separate GitHub repositories is cost-benefit justified.

Should it be one design type to one repository ? Or perhaps should all spring types be in one repository and all demo design types in a separate repository ? External contributor design types can each have their own separate repositories.

From today's conversation:

designtypes/Piston-Cylinder/load.sql -> Repo=Piston-Cylinder server/load.sql
client/public/designtypes/Piston-Cylinder/favicon.ico -> Repo=Piston-Cylinder client/public/favicon.ico
client/src/designtypes/Piston-Cylinder/code -> Repo=Piston-Cylinder client/src/code
client/docs/Help/DesignTypes/Piston-Cylinder/file.md -> Repo=Piston-Cylinder client/docs/Help/file.md

[1fifoto]

Create a script to populate a new repository with a minimum set of files for a new design type. Similar to React's create-react-app script.