Removed DestCharset for LDAP backends.

The internal characterset of OTRS is always utf-8 since OTRS 3.1.
The DestCharset setting in the LDAP customer backend is thus no
longer needed.
Using DBD utf8 switch for mysql

Previously, we stamped all data as utf8 in the OTRS DB object for
MySQL databases.

However this is not needed, there is a switch in DBD::mysql which
would make sure the C code already flags it as utf8.
Mark all data from DBD::Pg as utf8.

This will mark all data coming from DBD::Pg as utf8.

Also it will convert any data from non-UTF8 to UTF8 at the driver
level, which makes sure remote databases on PostgreSQL databases
that are for instance in LATIN1 present proper data in OTRS.

See http://bugs.otrs.org/show_bug.cgi?id=10005
Fix: customer data source in non-utf8 does not work.

See http://bugs.otrs.org/show_bug.cgi?id=10005

if you have a remote data source in non-utf8 the data was not
presented correctly.

the fix is to make the database library convert the data for you;
actually MySQL already did that for us. This caused double conversion
problems.
No conversion is needed in the CustomerUser::DB and CustomerCompany::DB
backends.
Revert "Using DBD utf8 switch for mysql"

This reverts commit b7e7df17024491526a324832ca286fa60020ba1d.

After this change we just had 1 test failing: Webservice.t

The problem is that if we use mysql_enable_utf8 only columns that
are defined as 'char', 'varchar', and 'text' have the utf-8 flag
on when retrieved from the database.

the config column in the web service history is not defined as
text but as a 'longblob':

    CREATE TABLE gi_webservice_config (
    id INTEGER NOT NULL AUTO_INCREMENT,
    name VARCHAR (200) NOT NULL,
    config LONGBLOB NOT NULL,
    ...

This retults in the config data returning to the database not to
have the utf-8 flag on.

If we'd upgrade the column to LONGTEXT, unittests will pass:

    ALTER TABLE gi_webservice_config CHANGE config config LONGTEXT NOT NULL;

But we actually have quite a lot columns defined as LONGBLOB where
they really should be LONGTEXT so I'll revert this change now.
Fixed: StandardTemplateList() generates invalid SQL (bug#10007).
Fixed release number.
Merge remote-tracking branch 'upstream/master'