Assettag UUID addition revert

Hey Julio,

Here is the revert PR for the AssetTag uuid addition requested by @JorgeFerrer.

On the other hand I have some questions or concerns regarding the revert. Jorge is right that the name of the AssetTag should be unique although adding a UUID won't affect that logic. I mean since we are just adding a new attribute, the way we handle the asset tags should be affected or changed either.

I can give you examples of other entities where attributes are funny too. Like for the User we have the UUID and the userId as well, and for a site templates we have a UUID too (besides the layoutSetPrototypeId), however the layout set prototype itself is a group.
These are not traditional uses of the UUID and an other ID combination(s) as well.

I'm not sure if I can see the issue with adding the UUID to the AssetTag. The logic and entity will be still intact, although we would need the UUID in the staging, and it would be hard to make this model to a StagedModel if we cannot add the UUID. Of course we should be careful with the asset tags, but this rule basically applies to any entity.

Thanks,

Máté

cc-ing: @KocsisDaniel