Refactor loading changesets from database rows ...

This both simplifies the codebase by reducing duplication, and also
fixes a bug where the committer info was never loaded from the database
rows because the load_* methods had never been updated with the
appropriate row/property setters.

Reimplemented changeset linking; version increment

Added 6th commit note parameter for changeset ID

Implemented selectable fixed issue assignment

Fix #121: Configurable bug fixed status change

Fix #114: lingering t_bug_data

Re-licensed the project under the MIT license

Fix #96: Allow vcs integration configuration hooks

Fix #62: Remove pass-by-reference for PHP 5.3+

Fix #51: Improved commit post-processing events ...

Rather than having separated post-processing events for checkin versus
import, the post-processing has been moved to the API function for
processing commit data.

The first post-process event "commits" allows plugins to get a list of
all changesets as they are checked in or imported.  The second event
"fixed" allows plugins to see a list of bugs that have been resolved by
changesets, along with the appropriate changeset, as described by
feature request #51.

This commit also removes the postcommit/postimport actions from the
MantisSourcePlugin interface, as they were a deemed uneccesary with the
new implementation, and generally should not be needed for VCS support.

Update copyrights for 2010

Issue #90: Move to direct-call framework design ...

Rather than signalling events everywhere and letting extension plugins
handle them if they choose to, the framework should be reworked to
directly call functions on the appropriate integration plugin. This will
both reduce overhead from events and simplify plugin work by removing if
statements at the beginning of every event handler.

This will require follow-on changes to all source integration plugins to
work with the new parent class API.

Version bump in Source plugin to signify API changes.

Attempt to fix duplicate row insertions

Fix errors with overlapping fixed/linked issues

Allow for correct processing of re-imported repos

Allow changeset loading to match the history order

Implement adding the repository name in bugnotes

Fix #50: Set info column on changeset table

Sometimes it seems like I don't even test anything

Missing semicolon

Improve fixed issue handling ...

Only set/update bug status, resolution, and fixed-in version when
appropriate.  Always send an update announcement via bug::update()
if the issue was updated, instead of only when a note is attached.

Make sure API uses raw config_get.

Fix #33: Fix OOM when deleting large repositories ...

Rather than having the delete process first load all changesets for the repo,
and then delete files for each individual changeset,  replace this method with
a single DB query that handles all file deletion with a subquery.

Fix #39: Look for exact repository name before using wildcards. ...

This modifies SourceRepo::load_by_name() to look for a repositoyr with the
exact name given first, and then fallback onto the old method of looking for
a repo that simply contains the given name.  This both addresses the problem
and maintains compatibility with the existing behavior and/or expectations.

Improve performance on large repositories.

Fix #28: Updated copyrights from '20081 to '2008-2009'

Fix #22: Make sure bugs exist before trying to update/resolve them.

Fix #21: Changed to using $X style placeholders in message template.

Fix #20: Implemented adding bugnotes for fixed bugs.

Issue #18: Initial implementation of user-vcs name associations.