Uploaded photos taken in inner adventure levels get assigned to wrong levels

[Toastbrot236]

When uploading a photo taken in a level in an adventure, LBP3 will only put the ID of the level itself (which will always be in the range of 1 - 15) into the request body and leave the ID of the adventure itself out, leading to the photos being assigned to wrong levels. LBP3 however also puts the root resource hash of the level into the SerializedPhotoLevel object, so a potential workaround could involve using that in combination with the newly introduced level revisions table.

[Toastbrot236]

Ok, it looks like the hash included by LBP3 in its photo uploads' rootLevel element is that of the level asset of the inner level. We can use the AssetDependencyRelations and the GameAssets tables to check whether there is any AdventureCreateProfile asset depending on the level asset, and if there is one, look up a level which references that dependent asset as root asset in either the GameLevel or the GameLevelRevisions tables to find out the adventure to attribute the photo to.

Then, we can use the id element in the photo upload, which we otherwise use to determine the level ID, to now determine the inner level's ID, which will be useful as soon as tracking inner adventure levels is implemented.

Before we do any of that, we can already determine whether a LBP3 photo was even taken in an adventure or just a regular level by finding out whether the hash in the rootLevel element already matches the root hash of a level in the database. If there is no such level, the photo was likely taken in an adventure.

EDIT: The method above is probably too hacky, and also inferior to just deserializing the adventure as recently suggested in #934, as that way, we can not only probably more easily obtain the level root hashes, but we can also assign them to inner IDs, and that way, also be able to attribute photos to specific inner levels, instead of just to the adventure.