Allow merge router, controller and action configuration

[popovserhii]

There is no way to use controller configuration in pair with router configuration.
For example, I develop a project which has front and admin parts.
Obviously, the project can have some default scripts for front and admin:

'routes' => [
	'front(.*)' => [
		'@front_js',
	],
	'admin(.*)' => [
		'@admin_js',
	],
]

But when I want to add a custom script for a controller the config above stop working, because AsseticBundle\Service::setupRenderer handle router configuration only when the controller configuration doesn't set.

This can be fixed with a simple change:

$controllerConfig = $this->getControllerConfig();
$actionConfig = $this->getActionConfig();
$config = array_merge($controllerConfig, $actionConfig);

if (count($config) == 0) {
	$config = $this->getRouterConfig();
}

to

$controllerConfig = $this->getControllerConfig();
$actionConfig = $this->getActionConfig();
$routerConfig = $this->getRouterConfig();
$config = array_merge($routerConfig, $controllerConfig, $actionConfig);

If you agree with this change I will do PR.

[widmogrod]

Hi @popovserhii,

I will gladly accept this PR, in addition to it, I would suggest one change.

• feature toggle - for merging configurations like bellow (default false - don't allow to merge for backward compatibility reasons)

$controllerConfig = $this->getControllerConfig();
$actionConfig = $this->getActionConfig();
$routerConfig = $this->getRouterConfig();

$mergeConfigs = $this->configuration->canMergeActionAndRouterConfig();
if ($mergeConfigs) {
  $config = array_merge($routerConfig, $controllerConfig, $actionConfig);
} else {
  // .. old way
}

What do you think?

[popovserhii]

It is even better. I will do PR in a few days.