Autogenerated EventType names not unique enough

[Cali0707]

Describe the bug
The current solution for autogenerated EventType names is not unique enough, leading to EventTypes which should be created not being created.

Expected behavior
Every new EventType to be seen by the AutoCreateEventType handler should have a new EventType created and stored.

To Reproduce
If #7089 is not merged, then send two events to a broker with the same name and namespace, where name + namespace is longer than ~10chars.

If #7089 is merged, then send two events to a channel or broker where the first ~10chars of the event.Type() are the same.

[pierDipi]

cc @matzew @dsimansk any thoughts here?

[dsimansk]

If #7089 is merged, then send two events to a channel or broker where the first ~10chars of the event.Type() are the same.

Given the PR is merged, we are in this case. How about taking the latter portion of event.Type() string as a priority. The types can be quiet lenghty with repetitive org, domain, package names. How about taking the last 10-20 chars as a base for the name?

[dsimansk]

/assign