Isolate @wip and @tba scenarios, add Cuke config

Scenarios/features marked with @tba are, in theory, still in the
analysis phase ("to be analyzed"), and aren't ready for development
yet.  I'm isolating the scenario I'm going to work on first by marking
it as @wip ("work in progress").
No-op auth step definitions for first @wip

Authorization and authentication are irrelevant for the first
scenario.  Until we are developing a scenario that relies on an
authentication or authorization *failure*, we can assume that all
users of the app are authorized to upload.  In practice, this could
even be combined with basic auth at the proxy server level,
essentially creating a single authorized "account."
First failing step, and decision point

This step, visiting the order log upload page, is the first step where
we have to implement an interface for the user.  In a real development
situation, we could take several paths here - the immediate
instantiation of a framework is by no means necessary, and might be
overkill - however, we know already we're writing a Rails app, so
this is where we'll add Rails.
Add almost-stock generated Rails app

Only a few modifications have been made to the default generated
Rails structure - the Gemfile has been simplified, we're not using
Test::Unit (we'll bring in rspec soon), and some cruft has been
removed (placeholder files, etc).
Add cucumber-rails and initialize schema.rb

We have to dump the schema.rb file, even though the schema is
currently empty, or Rails will complain when it tries to clone the
schema into the test database.  Cucumber is now running in the Rails
context and via a rake task, and we're back to the same failure we
had before we introduced Rails.