discovered while fixing #45

If you're in the UFO catalog and you pick up a mount from a UFO and move it to another spot in the UFO (or onto a different UFO) then the Bliz API shits the bed and gives bullshit data.

thanks to the Bliz API being shit, you can't reliably pick up a mount unless you know its displayIndex in the mount journal. Because this value is subject to change it was a stupid way to design the API. Change my mind.

So, instead, when the user picks up the mount from a UFO in the catalog I will store the valid data and then reuse it instead of using the shitty Bliz API when the user drops the mount back onto a UFO.

I think I need occupational therapy to recover from my Bliz PTSD.