Upgrade symfony CMF to 1.2, remove confusing parameters from getRouteByName*

From RouteProviderInterface, in the Routing CMF vendor package:

    /**
     * Find many routes by their names using the provided list of names.
     *
     * Note that this method may not throw an exception if some of the routes
     * are not found or are not actually Route instances. It will just return the
     * list of those Route instances it found.
     *
     * This method exists in order to allow performance optimizations. The
     * simple implementation could be to just repeatedly call
     * $this->getRouteByName() while catching and ignoring eventual exceptions.
     *
     * @param array $names      the list of names to retrieve
     * @param array $parameters DEPRECATED the parameters as they are passed to
     *      the UrlGeneratorInterface::generate call. (Only one array, not one
     *      for each entry in $names.
     *
     * @return \Symfony\Component\Routing\Route[] iterable thing with the keys
     *      the names of the $names argument.
     */

It's a deprecated and not useful part of the interface. We can/should just ignore it.

The interface and therefore the docblock are defined in Routing CMF. If you want to change the language of the docblock file a Pull Request here:

https://github.com/symfony-cmf/Routing

Here comes the thing ...

meh. it is probably rather that status.

FYI .. Routing 1.3 will likely be released in September but this time there are not major changes expected:
https://github.com/symfony-cmf/Routing/compare/1.2.0...master

However there is an open unfinished PR to add a RangedRouteProviderInterface by Daniel Wehner:
https://github.com/symfony-cmf/Routing/pull/101

To understand why this is important: because this leads to the understanding that routs are 'bare' objects. If you pass in parameters you'd think (I wasn't sure!) that somehow the route has those parameters.

Well, you sadly got moved to the wrong assumptions by that parameters. Technically having that combination (route name, parameters (and route))
is something which does not exist at a concept yet, neither in symfony/Routing nor in CMF. I could imagine though that it could
be really useful for those systems as well. Here is an issue in symfony to discuss it: https://github.com/symfony/symfony/issues/11642

We needed to fix some of our unit tests as well.

@chx
Given that I can understand that you might feel that I hijacked the issue, sorry in case.

@lsmith77
Ha, now you really want to force me getting that PR in :)

But it does in Drupal, right? Url.

Exactly, this is why I proposed that in the symfony issue as it is. The RouteMatch is a separate issue but certainly related.

Keeping up with our upstream dependencies is always appropriate, IMO, regardless of parameters or not. Thanks, dawehner!

Reroll

Committed c8bd0b4 and pushed to 8.0.x. Thanks!