Added DBIx- and Moose-related require statements.
Updated phrasing in manifest test file.

I believe this was automatically changed due to a package update.
Added schema for algorithms and referenced_work_guesses tables.
Updated tables to not cascade on delete or update.

The new version of DBIx::Class::Schema::Loader appears to have different
default behavior for the ON_DELETE and ON_UPDATE actions.  Previously, these
were set to "CASCADE," but now are "NO ACTION".  Also, the tables'
is_deferrable is now 0, instead of 1.
Added result classes Algorithm and ReferencedWorkGuess.

The Algorithm result class relates to the algorithms table, and is simply a
lookup table.  The ReferencedWorkGuess result class relates to the
referenced_work_guesses table.  This holds all of the guesses each uses has
made with an algorithm for what a work reference is referencing.  Relationship
were added (in the previous commit) in other classes, namely User and
WorkReference classes.  The Algorithm class also has a relationship to this
class.
Added user to referenced work guess unique key.

The unique constraint in the referenced_work_guesses table now includes the
user_id column, as well.  This means two different users can use the same
algorithm -- and version of that algorithm -- to make two different guesses.
For most automated situations, this will not be an issue, as if there are two
different users making a guess on a reference, they will use different
algorithms (or versions thereof).  If two are using the same algorithm, there
is probably no reason to both guess on the same references.  However, this
can most likely easily be covered in the application layer.

The important part here is if we have humans make manual guesses on
references.  Right now, users can change the actual referenced work.  But we
might want to make this a two-step process, where people put in guesses, and
only with a certain confidence, or approval, does the guess change the actual
reference.  The guesses people make would have the same "algorithm," and thus
would violate the previous version of the unique constraint.
Updated Result class with latest unique key.

See the previous commit message for the description of the key change and why
it was changed.
Removed the shebang line.

The shebang line that was here was out of date.  Removed it to more freely
use the script and whatever custom version of Perl is preferred.