Provide a diferent implementation for Seckit

[mariano-dagostino]

Problem:

• The seckit module uses a config file to define the directives of what to allow or block.
• The config is very complex to review, just a set of lines next each other.
• It also leaks internal stating or ddev environments.

Proposed solution

• Implement a SecKitEventSubscriber similar event subscriber.
• Provide a different, maybe per environment class to use arrays or yaml file with a different structure.
• Alternatively work in a seckit patch.

[AronNovak]

@mariano-dagostino I think we should not maintain an alternative way of configuring it, on the long run, it's better if we can provide a patch that helps everyone to do it right.