Halfway to Issue #1

*Massive* changes; yes, this should have been spaced out into multiple
commits.

* Full specs and coverage!
* CLI binstub actually runs Thor code;
* SimpleCov integrated into `spec/spec_helper.rb`;
* New `RubyAppUp::CLI` Thor class, with `#init` method/command;
* New `RubyAppUp::DescriptionMaker` class that is used to create the
text for the Gem's `long_desc` string;
* New `RubyAppUp::Repo` class encapsulates the Gem's understanding of a
Git repo;
* Updated README, including new "Configuration" section discussing
`OAUTH_TOKEN` environment variable;
* Gemspec has correct home page and also new dependent Gem references.

RSpec: 20 examples, 0 failures
RuboCop: 10 files inspected, no offences detected
Replaced `colorize` Gem with `pastel`.

Investigating whether mis-formatted output from `help init` was due to
(Windows-focused?) `fazibear/colorize` Gem or to Thor, replaced the Gem
with `peter-murach/pastel`, which incidentally has a few nice features
(currently in the `master` branch, but with an "imminent" formal
release), as embodied by the new `ColourScheme` class. Also, `pastel`
doesn't monkey-patch the String class as `colorize` does.
Cleaning up odds and ends.

Also known as "remember the difference between running `rake` and
`bundle exec rake`".

RSpec: 20 examples, 0 failures
RuboCop: 11 files inspected, no offences detected
Changing Git API Gems.

I won't be surprised if this needs fixing to pass CI, but IWOMM as best
I can tell, now that `pastel` 0.4.0 has been released and the code does
what the documentation has *said* it does (`#detach`) for some time.

Aruba was something I thought I'd need before I stumbled across RSpec
3's `output(…).to_stdout` matcher. Win!

The `github_api` Gem doesn't support things like cloning, and the
answer its author gave when asked was… a good working definition of
"highly suboptimal".

RSpec: 15 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
Killed inadvertently-committed test data.

And wrote some insurance in `repo_spec`.

RSpec: 15 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
`CLI#parse_repo_spec` now handles crap param.

RSpec: 15 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
Removed "invalid Github user" CLI spec.

See
https://github.com/jdickey/ruby_app_up/issues/1#issuecomment-64125728
for a discussion.

RSpec: 14 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
Dropping the repo_spec spec matching last commit.

Last adjustment to the new `git` Gem?

RSpec: 13 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
Commenting out as a reminder.

This needs a real fix; need to prove what the `git` gem does when given
invalid user name/repo credentials.

RSpec: 12 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
[Close #1] Version bump to 0.1.0.

RSpec: 12 examples, 0 failures
RuboCop: 12 files inspected, no offences detected
Merge pull request #2 from jdickey/issue-1

[Close #1] Clone a Git repo.

RSpec: 12 examples, 0 failures
RuboCop: 12 files inspected, no offences detected