qHash(Enum, size_t) may call an unexpected overload

During the investigation of QTBUG-106219 it was discovered that certain include-ordering has an effect on qHash(Enum, size_t).

If QKeySequence was included before qhashfunctions.h then the compiler would call a catch-all overload of qHash meant to allow old qHash implementations without a seed parameter to be called seamlessly without having to update the implementation. This overload xor's the seed with the result of qHash(Enum, 0) before returning it.

Usually qHash(Enum, size_t) will call qHash(int, size_t), and the biggest issue is that these two paths generate different hashes. So, as observed in QTBUG-106219, one could have a QHash container in one file and insert entries with one hash. Then, when the QHash container is moved and used in another file we end up trying to look up the key by a different hash, meaning we don't find any matches.