Asset3D and EncodedImage look the same at the component level

[jleibs]

There are potential weird behaviors in here:

• In particular, we don't want a visualizer option to show an EncodedImage as an Asset3D
• Additionally, logging Asset3D and a compressed image to the same entity will break in unexpected ways

[jleibs]

We might be able to punt on this until we have tagged components:

• #6889

[emilk]

One symptom of this is that every EncodedImage has an option to add it to a 3D space view:

[Wumpf]

This is solved now due to tagged components: we can easily distinguish what kind of blob etc. is present, causing some simplifications