Store hash strings separately in gvdb for resources
Submitted by Alexander Larsson
GResources uses gvdb instances with pretty large hash items, and right now gvdb intermixes the path strings used for the hashtable lookup with the actual hash item data. This means hashtable lookups will be touching a lot of memory that might otherwise not be mapped it.
It would be more efficient (and binary compatible) if we put all the strings used for the keys in a single place, thus avoiding to touch the memory with the data when doing lookups.