Custom room types shouldn't log spam

[redstrate]

So I started using libQuotient in a project and it uses a custom room type for some functionality. However, libQuotient is not pleased about this at all. It will remind me constantly in another libQutoient consumer, for example NeoChat:

2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
2024-08-28T15:14:30 [WARN ] quotient.events: /home/josh/kde/src/libquotient/Quotient/converters.cpp:13: void Quotient::_impl::warnUnknownEnumValue(const QString&, const char*): Unknown RoomType value: zone.xiv.astra-sync
...
(a bunch more)

I can easily fix this, but I don't exactly how I should. Would it be enough to change this from a warning to a debug message or?

[KitsuneRal]

Now that I see the case I actually wonder if it's worth having this message at all. I guess, let's just drop it.

[redstrate]

Now that I see the case I actually wonder if it's worth having this message at all. I guess, let's just drop it.

Drop the unknown enum value message mechanism entirely or just for this one case?