Make sure essentials adds the targeting shared api to the root pom similar to hippo-enterprise-services

After some more thinking, we decided to NOT have the hippo-addon-targeting-shared-api automatically being added to a project via the hippo-cms7-enterprise-release pom : The downside is namely that even if customers did not include relevance (targeting), they still have it in their mvn cargo.run profile as a shared lib. Although it is not that harmful, it is not inline with how we manage hippo-enterprise-services. The choice was to handle hippo-enterprise-services like we manage hippo-addon-targeting-shared-api or the other way around.

Most safe choice for now is to stick to how it works for hippo-enterprise-services : when selecting the 'projects' feature in essentials, essentials takes care of adding all required dependencies, including appending the cargo.run profile.

It is easier later to change the behavior we now opt for than the other way around where the hippo-cms7-enterprise-release pom would already include hippo-addon-targeting-shared-api and hippo-enterprise-services to the cargo.run profile, regardless of whether targeting or projects is actually included in the end project