Activate multilingual route extraction and translation

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | ---
| Fixed tickets | ---
| Refs tickets  | #1793, https://github.com/schmittjoh/JMSTranslationBundle/issues/201
| License       | MIT
| Doc PR        | ---


- Globally ignore @type annotation. Necessary to be able to use the extended array documentation syntax (which is used in the Core):
   
    ```php
    /**
     * Related to getRegistrationErrors, returns error information related to a new or modified e-mail address.
     *
     * @param mixed[] $args {
     *      @type int    $uid        The uid of the user to be checked; optional.
     *      @type string $email      The e-mail address to be checked.
     *      @type string $emailagain The repeated e-mail address entered by the user for verification.
     *                      }
     *
     * @return array An array of error information organized by registration form field.
     */
    ```
- *Moved Doctrine service alias from Zikula Event (core preinit) to CompilerPass.* This is necessary to have the alias available even if the **Zikula** Core is not booted (e.g. if a Symfony console command is used).
- Made the multilingual routing working. I needed to introduce two global variables in the process, to be able to filter the routes by module.

To translate routes, make sure the module is correctly installed, then run:

    php app/console translation:extract LOCALE --bundle=BUNDLENAME  --enable-extractor=jms_i18n_routing --output-format=po

e.g.

    php app/console translation:extract de --bundle=ZikulaUsersModule  --enable-extractor=jms_i18n_routing --output-format=po

This creates a `translations` folder in the bundle's `Resources` folder with a `.po` file in it. Translate it as usual.

Note:
You can also use other formats, however **xliff** is the suggested one.

    [0] => php
    [1] => xlf
    [2] => po
    [3] => mo
    [4] => yml
    [5] => ts
    [6] => csv
    [7] => ini
    [8] => json
    [9] => res
    [10] => xliff

Note 2:
If you receive PHP notices / warnings while running the command, it might probably [this bug](https://github.com/schmittjoh/JMSTranslationBundle/issues/201) and can be *ignored*.
This makes sure to only include routes in the translation file which are part of the module being translated.