Removed Rake support and handling

Removed the auto-generated rake task stuff and reworked the README
to remove all rake mentions and set up for more CLI and configuration
documentation.
Merge pull request #105 from redding/kr-rmrake

Removed Rake support and handling
have the CLI sort the test files before requiring them

This ensures the tests will be added, run, and their results all
displayed in a consistant order.  The dir globbing introduced by the
cli was not returning paths in alpha-numeric order.  This ensures
test files are required in alpha-num order.
Merge pull request #107 from redding/kr-testorder

have the CLI sort the test files before requiring them
moved the capture output helper into the common set of helpers

It really should be common and included on the base view b/c there
is a global config option that drives whether to capture output or
not.
Merge pull request #108 from redding/kr-viewupd

moved the capture output helper into the common set of helpers
update README for new config/init pattern

This reworks the README to instruct how to configure assert using the
new config/init pattern.
added the config/init pattern for initializing Assert

This removes all the crappy setup files and puts the init logic
in the CLIRunner class.  This also centralizes all settings on a
Config singleton.  This is the central place all settings are read
from and where User, Local, CLI, and ENV settings will be applied.
Merge pull request #106 from redding/kr-configinit

use a config/init pattern
updated Runner handling to configure runner instances

You now configure a Runner instance.  There are a couple reasons for
this.

One, the user may need to do custom Runner initialization and its
easier to let them do it and config Assert with an instance.  It's
never good to be creating instances of things on behalf of the users.

Two, this is more consistant with how you configure a View or a Suite -
you just pass an instance.
Merge pull request #109 from redding/kr-runnerupd

updated Runner handling to configure runner instances
added in requiring a local settings file on initialization

This allows for settings that are specific to a project.  By default,
Assert will look for the file at `./.assert.rb`.  You can specify
a custom local settings file by setting the `ASSERT_LOCALFILE` env
var.
Merge pull request #110 from redding/kr-localsettings

added in requiring a local settings file on initialization
handle and apply options from the CLI

This updates the initialization to parse and honor CLI options.  There
are options for the runner seed, output, halt on fail and debug
handling.
renamed `output` option to `show_output`

Trying to more clear about the option's intent.
Merge pull request #111 from redding/kr-cliopts

handle and apply options from the CLI
reorganized the result backtrace filtering logic

This is just a minor reorg and cleanup - no behavior changes.
handle and apply ENV settings

This updates the initialization to honor env var settings.  Right
now, runner_seed is the only setting driven by an env var.

I chose to remove the boolean options from the env settings b/c
of difficulty in parsing and the ambiguity in handling the values
parsed.  Ultimately it's easier to just use the flags anyway.  We
can always handle them at a later time.

Closes #98.
Closes #99.
Merge pull request #112 from redding/kr-envopts

handle and apply ENV settings
moved test file loading into the `Assert.init` method

Realized its probably better to let the `init` method control all
init behavior, including loading test files and firing view events.
This really isn't the business of the `AssertRunner` and before the
init behavior was divided.

This also updates the signature of the `init` method to take an
options hash.  This is for future behavior expansion.