Emit warning when mixing node types on an entity

## What problem does this solve or what need does it fill?

Currently there is no warning emitted if you create an entity that has both `Node` and `Text` components, or `Node` and `ImageNode` and so on. However, this will not behave as expected; my understanding is that an entity should only have one `...Node` component.

I've make this mistake myself, and I've seen at least one post on the discord from someone who also did this without realizing it was incorrect.

## What solution would you like?

Emit a warning when mixing incompatible components like Node. For now, I suggest doing the specific case of `Node`, and not trying to solve the general problem of incompatible components.

Start by locating the code that handles Node components and entity composition, then review how Text and ImageNode are attached. Done means an entity combining Node with another node type emits a warning, while the requested scope remains limited to the specific Node case.

Written by the indexing model from the issue text.