Correct display custom status in cross-project relationships

In the bug relationships section in view.php, the target bug's status
was incorrectly displayed as "@X@" (where X is the status_enum id) if
the following conditions were true:
 - the target bug is in a different project
 - it is a custom status

This commit fixes the behavior, and displays the corresponding enum
element's language string.

2 new parameters have been added to function get_enum_element(): user
and project id (defaulted to null to preserve existing behavior). These
parameters are passed on to config_get() call, allowing to specify the
context for retrieving the enum element.

The call to get_enum_element() in function relationship_get_details()
has been altered to specify the target bug's project id.

Fixes #11323
Additional fixes for display of custom status

Resolves additional display issues of custom status cross-project, similar
to what was fixed in 324dbb4681255b7a1fa4cc309ab8742f028dbf43. These
can occur when "All Projects" is selected and one or more projects have
custom statuses not defined globally, in the following pages:

 - View Issues
 - Change Log
 - Roadmap
 - Sponsorship

Affects #11323
Code cleanup and optimization

 - fix whitespace errors
 - align to coding guidelines
 - moved variable initialization out of for loop
Fix cross-project display of custom status colors

When a custom status is defined in a different project, its custom
color was not used (displayed white) in the following cases

- view issue details page, relationship
- View Issues
- My View
- Sponsorship
- Bug group action list

Fixes #13682
Fix cross-project display of custom resolution codes

When a custom resolution is defined in a different project, its code
was displayed as @X@ instead of the corresponding string in the
resolution column, as well as when hovering over the status in the view
issues page.

Fixes #13707
Fix cross-project display of custom severity and priority

When a custom severity is defined in a different project, its code
was displayed as @X@ instead of the corresponding string in the
severity column on the View Issues page.

The same problem applied to custom priorities

Fixes #13718
More fixes of custom enum types across projects

Fixes #13728
Fix custom enum types across projects in exports

The CSV and Excel exports, as well as printing a report to Word now
properly handle custom enums when dealing with bugs from different
projects.

Fixes #13728
Add support for SQL Server Native driver

Since PHP 5.3 has been released, as per PHP documentation the mssql
driver is no longer available on Windows. Microsoft has published a
new SQL Server Native Driver.

This commits adds support for this new driver (sqlsrv) to MantisBT
as mssqlnative db type.

Thanks to genius_p and tomkraw1 for the original patch and testing.

Fixes #11776
Removed extraneous call to user_reset_password()

This should have been removed as part of cc6198207f896094252631947c456a192c74d97d
Thanks to dhx for catching this oversight.

Affects #13690
Fix #13789 : Invalid usage of function mci_soap_fault_access_denied
Added ignores.
Added missing opening quote
Moved KDevelop ignores to IDE ignores
Fix use of undefined $t_bug variable instead of $p_bug

Copy/paste error introduced in 735506cfc14aab75cacb3adaf79d21a16dfe3992

Affects #11323
New logo, button and favicon.

1. Logo - for now login page and normal pages use the same logo size.  In future versions, we may include a slightly larger one for the login page.  Didn't want to include this in a minor update, since this is a configurable image name, and hence adding a new logo, may end up with having a mix of two logos.

2. The button is now a scaled version of the logo.  For this reason, it is removed from the footer of the login page, but kept on the others.

3. Added the new favicon.
Fix 0013901: SOAP API allows invoking methods without proper authentication

Note: only applied to 1.2.x not 'next', as the code is changing anyway
Fix #13696: Show absolute_path_default_upload_folder on edit project page

Fix of #8250 did the same for the create project page
Fix #13941: Missing newlines in Word export
Fix #13935: Version-based filtering not possible

Commit a68398245663d25229800638b6965ffe6e7ab0d3 for bug #13096
introduced a regression in version-based filtering due to not properly
dealing with selected version parameter when passed as an array.