Separate string for changeset column title

Bumped framework version

Changeset column improvements

Initial draft of a changeset count column

Fix update query to use single quotes

Touch last_updated when attaching changesets

Fix #145: Full import creates bad history entries

Fix #144: Proper changeset processing order ...

When commiting changesets that resolve an issue, the changeset data
should be saved to the database before beginning to modify the issue
data.  This is to fix a problem of generating an email with a change
history that did not show the attached changesets, which could be
confusing in certain cases.

Fix #110: Non-unique index name in schema block 13

Fix #131: Reversed history entry

Fix #143: Lingering hardcoded strings

Fix #142: Added German translation strings ...

Signed-off-by: John Reese <jreese@leetcode.net>

Bug fixes for resolving commits

F/U 6999df13: Use proper repo object

Include repo name in history entries for clarity

Fix #135: Added French translation for core+websvn ...

Signed-off-by: John Reese <jreese@leetcode.net>

Fix #134: Lingering hardcoded language strings ...

Signed-off-by: John Reese <jreese@leetcode.net>

Fix #136: Only output cell if using porting status ...

Signed-off-by: John Reese <jreese@leetcode.net>

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

Update JS behavior to use portable jQuery methods

Fix #129: Set default table collation to utf8

Fix #122: Implement method to edit changeset data ...

Enhances the existing update method for porting status with a full edit
page allowing the user to update the following changeset data:

- Author's user ID
- Committer's user ID
- Changeset branch
- Porting status
- Commit message

Also fixes an issue where users without update access can still see the
dropdown and update form for porting status.

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.

Added named link to changeset rows for hyperlinks

Hook changeset linking later in page load

Reimplemented changeset linking; version increment

Added 6th commit note parameter for changeset ID

Implemented selectable fixed issue assignment