Follow up to previous commit to fix versions

Separate remote import page from user imports ...

Due to complexities of trying to have both user-initiated imports and
remote imports handled in the same page, the import process has been
split into two separate use cases.  pages/import.php is now specifically
for use by the remote import process, while pages/repo_import_latest.php
remains for usage by authenticated MantisBT users.

This will require that all cronjobs or post-commit hooks that triggered
a remote import be updated to point to the new import url.  Framework
version has been bumped accordingly.

Version removed from lang/ by translator request

Fix #129: Set default table collation to utf8

Hook changeset linking later in page load

Reimplemented changeset linking; version increment

Implemented selectable fixed issue assignment

Fix #121: Configurable bug fixed status change

Re-licensed the project under the MIT license

Fix #97: Refacter core SVN into shared codebase ...

Created base SVN plugin with the shared SVN code from WebSVN and SFSVN
plugins, and then modified the previous plugins to inherit from the new
base plugin.  This will end the previous need to constantly replicate
changes between the two SVN plugins.

Currently, the only way to modify shared SVN configuration is to have
the base SVN plugin installed, but this is a task for a different
commit.

Fix #95: Imcomplete event API changeover

Fix #71: Updated default regexes to require #bug ...

To prevent inadvertantly marking issues as fixed, the default buglink
regexes have been modified to require using the # symbol in front of bug
numbers in commit messages.  This also has the added benefit of ensuring
that valid buglink matches will also be marked up correctly when viewing
messages in MantisBT.

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.

Implemented dynamic search filter reduction ...

When selecting a source control type or repository, the repository and
branch list options will be dynamically reduced to match the user
selections.

This is an optional enhancement for installations with the jQuery
plugin installed.

Updated default regexen to allow passive tense

Allow repo statistics to be disabled.

Fix #32: XL columns should not have default values.

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

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

Issue #20: Added configuration settings for enabling and setting bug fixed messages.

Fix #18: Added configurable threshold for setting vcs username.

Isue #18: Added unique index to enforce username constraint.

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

Fix #13: Convert project license to AGPL3.

Issue #11: Implemented repo management form for updating/creating branch mappings. Switch to storing versions as strings.

Issue #11: Defined basic mapping strategies and names.

Issue #11: Configuration settings to enable/disable branch mapping.

Issue #11: Schema definition for branch mapping.