new settings page that allows plugins to integrate their own settings dialogs more with the existing ones

Used the current plugin system to define `USER_OC_LDAP` class
that can be used as backend for OC_USER

It's possible to use `OC_USER` as normal but the real stuff
is done by the `OC_USER::$_backend` class, setted using
`OC_USER::setBackend()` (this is done in inc/lib_user.php)

At start the choosen user manager is created
(e.g. OC_USER_DATABASE, OC_USER_LDAP)
and put into the global variable `$userManager`.

This is the variable to use instead of `OC_USER` class.

TODO: A better name than $userManager?

  * camelCase
  * spaces here and there

  * Added spaces here and there
  * Using camelCase for same variable

  * Using camelCase for `$classType` property
  * Using `self` keyword instead of class name
  * Added spaces here and there

  * Support numeric types too
  * $WEBROOT variable was not necessary

This actually write all the key/value into the config.php.
The code in `writeAdminLisener()` is cleaner.
This is in prevision of new configuration options (e.g. plugin related)

Here the types added:
  * Flac / Ogg [1]
  * GZip / Tar / Tar+GZip
  * PDF / SVG / Tiff
  * JavaScript

Other little changes:
  * I changed the ordered to be alphabetical (by extension)
  * Using single quotes instead of double quotes for strings
  * Indentation

[1]: http://wiki.xiph.org/MIME_Types_and_File_Extensions
[2]: http://www.asciitable.it/mimetypes.asp

PHP function names is case-insensitive so this change isn't
intrusive but improve readability of the code.