Improve error handling for misuse of content component

In a new project a developer accidentally used the EssentialsContentComponent for his custom hst:catalog component instead of the EssentialsDocumentComponent. The resulting component could not be added to a container with the feedback from the system just being "Couldn't add mycomponent". Nothing in the logs. This was hard to diagnose and the mistake an easy one to make (the components sound very similar). The error handling/logging should be improved.

Reproduction

Create a 12.1 archetype project

accept Essentials defaults

add simple content feautre

add hst catalog item with componentclassname EssentailsContentComponent

add the hst catalog item to a prototype page instance

Observed

error message "cannot add xyzcomponent"

nothing in logs

component is added anyway

Suggested Improvement

Error message in console explaining why component is broken (no bean found?)