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

まず、issue に記載されているエンジン設定とプロセス定義の読み込みメカニズムを追跡し、次に BPMN のプロセスレベル拡張がどのように表現され、読み取られるかを調査します。コードを変更する前に、実行グループ化の形式と包含・除外のルールをメンテナーと確認します。対象となる定義が読み込まれ、対象外の共有データベース定義が無視され、選択した設定動作に対するカバレッジがある状態を完了とします。

索引モデルが issue の本文から書いたものです。