added flag parameter for enabling AuditController

[p365labs]

@DamienHarper & @maxhelias Hi all, I implemented a solution to programmatically disable AuditController::class,
this way a new configuration parameter could be set to false and that controller and its routes won't be available.

The use case to cover is a use case in which the library is used to store informatin on the persistence layer but they will be available in a different way to the user, for example through API.
The controller routes won't be exposed to any environment.

The parameter is:

• enable_audit_controller

and has been added to the Configuration.php file.

• default value is true

reference issue #153

[DamienHarper]

@p365labs thanks for the contribution.
Though, your PR does not do exactly what you expect it to do: the compiler pass removes the controller definition but routes still get registered and trying to access such a route triggers a LogicException with message "DH\DoctrineAuditBundle\Controller\AuditController" has no container set, did you forget to define it as a service subscriber?

[p365labs]

Hi, @DamienHarper you're right, I missed a piece.
Right now I've implemented a custom route loader which based on parameter flag,
loads the annotations from the controller.

[maxhelias]

I haven't tested yet but it looks very promising

[maxhelias]

I haven't tested yet but that seems good to me

[DamienHarper]

Looks good to me, thanks for the contribution!

[DamienHarper]

@p365labs a conflict remains about composer.json. Please, fix it so that I can merge ;)

[p365labs]

@DamienHarper my fault, I probably forgot to rebase from master. now should be ok.