Issue #13998: Logo is not present on new installation.

- Updated config_inc_sample.php to use the new logo filename.
- Commented out all configuration options that are optional (i.e. all except db and email).
Issue #13998: Logo is not present on new installation.

1. Rename the mantis_logo_238x40.png to mantis_logo.png.  To avoid more renames in the future if we change the logo size or design.
2. Added a copy of mantis_logo.png in gif format to match the old file name, just in case config_inc.php points to it.  Note that the gif version is a lower quality due to the gif format.
3. Changed the code, default configuration, and sample configuration to reference mantis_logo.png.
Update version to 1.2.10
Updated release notes for 1.2.9

A bit late but better than never
Updated doc/RELEASE for 1.2.10.
Fixes #14013: System notice in bug_check_workflow().

If the status workflow is defined, but there is no corresponding entry to the current state, then allow all statuses.  The reasoning is that there should always be at least one possible next status.
Fix tag attach/detach for non-admin users
Fix tag attach/detach for non-admin users

Take 2, thanks to atrol for keeping his eyes open.
Code cleanup in excel_xml_export.php

Removed the specific logic to handle the extended text fields, which is
no longer required as the BugData API will automatically retrieve them
if needed. This is a leftover from the conversion from old, array-style
access to bug data (see 18ad379c92db070115b8921bd51024b5bb5dd230).

Furthermore, the call to bug_get() was redundant, since the result set
from filter_get_bug_rows() already contains BugData objects.

Fixes #14017

Also removes a useless line of code accidentally left in there by commit
b5450f3d7eedf5669affe77865560cbf053bbead.
Localisation updates from http://translatewiki.net.
Fix #14014: Search number > 2147483647 fails on 64-bit systems

When a numeric search term is entered, the Filter API will only check
for matches in the bug and bugnote id fields when the search term is
within a valid range.

This was never an issue on 32-bit systems, but on 64-bit OS, PostgreSQL
throws an "integer out of range" error when executing the query because
the search term is cast to (int) and PHP_INT_MAX is greater than the
largest value allowed for the numeric DB fields (4-byte int, 2^31-1).

This issue does not exist on MySQL as the value is capped to the maximum
allowed; behavior was not tested on Oracle, DB2 or MSSQL.

The fix for PostgreSQL behavior is a hack, but I can't think of any
better solution (ideally, we should be able to query the DB for the
maximum allowed value for a field).
Add multiple file upload functionality

Adds a new option in config_defaults_inc.php (file_upload_max_num) to
determine how many files can be simultaneously uploaded.

Modifies the code in issue reporting and view details pages, to enable
the new functionality.

Fixes #5228
Fix whitespace and code alignment, removed useless code
Add multi-file upload to bug reporting page

Fixes #5228
I18l support for multi-file upload

Adds new strings to handle the plurals when uploading multiple files
(e.g. "Upload File" / "Upload Files") and conditionally display the
appropriate one depending on value of file_upload_max_num

Fixes #5228
Remove duplicate error code and message

There were two separate error constants defined, ERROR_DUPLICATE_FILE
and ERROR_FILE_DUPLICATE, corresponding to an error message string with
identical text.

This commit removes the redundant constant ERROR_DUPLICATE_FILE and the
corresponding error message.

Fixes #5228
Document g_file_upload_max_num in the administration guide

Affects #5228: Attaching multiple files in one go.
Removing previous checkins in preparation for 1.2.10.  Will re-do just before release.

Revert "Updated doc/RELEASE for 1.2.10."

This reverts commit a817c2cb10d5e26a7a5083f5ad1cce6168fddabf.
Revert "Update version to 1.2.10"

This reverts commit 1c1e04736ff5a6f57049cee5056fbad00392fba5.
Updated MantisTouch website url in the manual.