Avoid creating an empty default Camel context in Camel CDI

Camel CDI automatically deploys a Camel context to avoid user having to explicitly declare one.

However, if the user mis-configures her/his application so that there is no route nor any other active components configured (like consumers), that leads to having an empty Camel context started.

Besides, in Camel WildFly, the subsystem automatically deploys the Camel CDI extension even in the case the user does not intent to use it, which leads to having an empty Camel context started.

In both cases, the Camel CDI extension could rely on an heuristic (no routes, no consumers, ...) to avoid deploying that empty Camel context.