Add setup script to configure ci on target repo

[dennisjbell]

[PRIMARY] script is run from base of target repo, and sets up ci and spec directories

[SECONDARY] can be run on existing systems to update base components, but will not alter repo-altered components - instead it will compare to previous version via sha hashes and then provide diffs so user can take appropriate actions. (or some similar behaviour that allows new functionality to be introduced while not losing repo-specific-changes - similar to how rails behaves when generating over an existing project)