Allow the engine to handle only certain definitions

In some cases it is convenient many Flowable engines to share a single database and tables set. But then it is possible the environment of each engine to not satisfy the requirements of each process definition, for example the engine instance environment may not contain/provide the required delegates (implementations of `org.flowable.engine.delegate.JavaDelegate`).

To overcome this inconvenience:
1. Develop a BPMN extension on process level, which to define process definition execution grouping;

2. Add in the engine configuration a parameter to define a list of process definition "groups" this engine instance to handle. The parameter should also allow definition of a list with exclusions, i.e. which process definitions the engine instance to **not** handle. The existence of both lists in the same configuration seems meaningless, except in the case the list definition allows wildcards or regular expressions. The allowance of wildcards and regular expressions in the lists should be further decided by the Folwable Engine development management;

3. Implement a filter in the engine's process definitions loading mechanism to load only the eligible (according to the engine configuration) definitions from the database;

4. Process definition eligibility description using process definition identifier (key) or name is out of scope. The eligibility of specific process definitions should be also defined using the "execution grouping" BPMN extension.

Note: This issue is based on the forum discussion http://forum.flowable.org/t/restrict-the-engine-to-handle-only-certain-definitions/245

Comienza rastreando la configuración del motor y el mecanismo de carga de definiciones de procesos descritos en la issue, y después inspecciona cómo se representan y leen las extensiones a nivel de proceso de BPMN. Aclara con las personas mantenedoras el formato de agrupación de ejecución y las reglas de inclusión o exclusión antes de cambiar el código. Se considera terminado cuando se cargan las definiciones elegibles, mientras que se ignoran las definiciones no elegibles de bases de datos compartidas, con cobertura para el comportamiento de configuración elegido.

Escrito por el modelo de indexación a partir del texto del issue.